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

Empty extension - ghost logging #3593

Closed
waderyan opened this issue Mar 1, 2016 · 5 comments
Closed

Empty extension - ghost logging #3593

waderyan opened this issue Mar 1, 2016 · 5 comments
Assignees
Labels
*question Issue represents a question, should be posted to StackOverflow (VS Code)

Comments

@waderyan
Copy link

waderyan commented Mar 1, 2016

This is strange to me. I created an extension for adding json validation to babelrc files. I removed everything that was unnecessary including any .js file.

When I debug my extension, the default console.log seems to run.

image

See the log "Spell and Grammar checker active...". This is the same log from spell and grammar check extension.

I don't know if this is causing problems... but its strange behavior to me. Why is this happening?

@waderyan waderyan added the *question Issue represents a question, should be posted to StackOverflow (VS Code) label Mar 1, 2016
@weinand
Copy link
Contributor

weinand commented Mar 1, 2016

@waderyan what is strange here? You are launching another instance of the extension host. It runs the same extensions that you have installed (e.g. the 'Spell and Grammar checker) plus your extension under development. So this looks quite normal to me.

CC @bpasero do you agree?

@bpasero
Copy link
Member

bpasero commented Mar 2, 2016

Yes, console.log goes to the repl from the extension!

@waderyan
Copy link
Author

waderyan commented Mar 2, 2016

@weinand I don't understand how I installed the Spell and Grammar checker extension. Shouldn't I only see the console.log from the extension I am currently debugging? Why do I see another installed extension?

@bpasero
Copy link
Member

bpasero commented Mar 2, 2016

Actually we do not distinguish console.log from your extension or any other extension which is somewhat odd. Maybe we should not load any extension BUT the one you are debugging?

@weinand
Copy link
Contributor

weinand commented Mar 2, 2016

@waderyan you are really debugging the extension host and not only your extension. And the extension host has access to all extensions plus your additional extension.

@weinand weinand closed this as completed Mar 8, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*question Issue represents a question, should be posted to StackOverflow (VS Code)
Projects
None yet
Development

No branches or pull requests

3 participants