Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Panel configuration: multiple outputs #1413

Closed
jeremylan opened this issue May 18, 2018 · 11 comments
Closed

Panel configuration: multiple outputs #1413

jeremylan opened this issue May 18, 2018 · 11 comments

Comments

@jeremylan
Copy link

Hi

Thank you for this great project.

I'm using to write some React Native code, and I'm having a problem with the output panel multiple outputs.

There are two outputs in the panel:

Output:SublimeLinter
Output:SublimeLinter Messages

Ideally I would always like to see the error outputs in SublimeLinter only. If I switch manually to the right output, at every save the plugin will switch automatically to SublimeLinter Messages instead which is very annoying.

Is there any way to disable that particular Output only? I tried searching in the Settings and I even looked at the code in message_view.py but could not find anything.

Any idea?

Thanks

screen shot 2018-05-18 at 1 52 14 pm

@kaste
Copy link
Contributor

kaste commented May 18, 2018

Hi 👋

Usually you shouldn't see the Message panel at all bc it opens only on unhandled errors.

In this case, eslint puts something on stderr that maybe shouldn't be there.

Please post the error message. Think about the eslint message. Is it something you can turn off via eslintrc.

@jeremylan
Copy link
Author

Hi

Thanks for the quick reply.

The error is created by an issue in node-fs-extra, there is a fix already merged for next version of Node:

Pull Request

The error is:

SublimeLinter: #167 eslint index.js ERROR:
========================================== 

(node:18029) ExperimentalWarning: The fs.promises API is experimental

I understand this error will disappear when the new node is released but for my curiosity is there a way to control the output panels via SublimeLinter settings or eslintrc?

I could not really find any documentation on this, and the SublimeText build system output documentation is not the easiest at a quick glance...

Thanks

@braver
Copy link
Member

braver commented May 18, 2018

I think this goes into the same category as DeprecationWarning, and I believe we suppress those.

@kaste
Copy link
Contributor

kaste commented May 18, 2018

Yes, must be solved in eslint repo.

@kaste
Copy link
Contributor

kaste commented May 18, 2018

@braver braver closed this as completed May 18, 2018
@braver
Copy link
Member

braver commented May 18, 2018

@jeremylan @kaste I'm yak shaving and waiting for builds to complete anyway: SublimeLinter/SublimeLinter-eslint#250

@jeremylan
Copy link
Author

Thanks I had forked and was creating a PR and saw you've already done it @braver!
I'll delete the fork now

Thanks for the prompt resolution :)

@kaste
Copy link
Contributor

kaste commented May 18, 2018

Hi again. I have a question.

You have the following

(node:18029) ExperimentalWarning: The fs.promises API is experimental

Where is that (node:18029) coming from? Is this number an ever changing pid (ProcessID)? I'm asking bc when we post errors on the Message panel, we post every unique error only once to reduce annoyingness. Obviously, if this pid changes all the time the error pops up all the time. You cannot dismiss it so to speak.

Can this additional output configured?

@jeremylan
Copy link
Author

Hi @kaste

I assume that is the pid.
You can see the error description here:

jprichardson/node-fs-extra#578 (comment)

It's all output from the Node code I guess.

I can confirm yesterday's fix worked, I updated the eslint package and it's all working

@kaste
Copy link
Contributor

kaste commented May 19, 2018

@braver Do you also see this output (node:xxx)? I don't have it.

@braver
Copy link
Member

braver commented May 19, 2018

@kaste my laptop’s battery died, so I can’t check until later next week...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants