-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
terminal output tab - autoopen problem #81522
Comments
/needsMoreInfo Does this occur with all extensions disabled? ( (Note that you are on an older version of VS Code, please update.) |
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue. Happy Coding! |
i am also facing the same problem. it is very much annoying |
@dextar1 Does this occur with all extensions disabled? ( |
It has not opened again yet, I will try it, for more info logs come from PHP Language Server, is it mean that problem in extensions? |
/causedByExtension Yes, please file an issue with the PHP extension you have installed. |
This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. Happy Coding! |
@chrmarti this has already been filed on the PHP extension. |
It feels like there should be a way to disable this automatic opening, even on error, when using extensions which do a lot of parsing, like vscode-php-intellisense - perhaps a global option that stops the tab being opened on errror, and a report of error counts on the bottom status bar which when clicked opens the output window? |
@felixfbecker this is actually fully under your control. The default is that the LSP client reveals the output channel if an error is logged into it. However when creating the client you can set this to If this doesn't work for you please open an issue in the |
Just to be clear: the output channel comes to front if an error is logged to it which for example is the case when a server errors a response. |
According to the comment linked above, there was no error in the output channel (I can't personally reproduce it, I'm only forwarding) |
How does the output panel look like? VS Code has no error concept in output channels. It is LSP specific (e.g. |
@dbaeumer What you mean, saying how it's look like? |
Can you just add an option to not auto switch even if there is an output, because i have the same issue. It is fucking annoying as hell, when i try to type something in the terminal it switches me over to output every 0.3s. I really like the idea of an integrated terminal, but i have to use iterm2 for now because of this bug :( |
How to add this option? |
@ashot11091950 Seems like it is not a VS Code bug, its just a plugin "PHP Language Server" that is calling the reveal output aggressively. You have to report the issue to them. Until then you can just disable the PHP plugin, to find it just disable all the PHP one by one until the issue stops :) |
Issue Type: Bug
terminal output tab everytime opens and shows info about parsing files, when I close tab, it reopens after delay
VS Code version: Code 1.36.1 (2213894, 2019-07-08T22:55:08.091Z)
OS version: Linux x64 4.15.0-64-generic
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: disabled_software
skia_deferred_display_list: disabled_off
skia_renderer: disabled_off
surface_synchronization: enabled_on
video_decode: unavailable_off
viz_display_compositor: disabled_off
webgl: enabled
webgl2: enabled
Extensions (3)
The text was updated successfully, but these errors were encountered: