Question:
Currently when one types a term in the search-bar of the settings-UI and no matching settings are found then a Clear Search option appears which deletes the term in the search-bar if clicked. However, this option does not appear when matching settings are found. If one wants now to remove the term from the search-bar one has to manually select the typed term and press the delete-button. It would be more convenient if there always would be a 'Delete Search'-Button. This could be a little X symbol on the right of the search-bar. Currently when the Clear Search option is clicked the search-term is deleted but the search-bar loses focus. It would be more convenient if the search-bar would get the focus such that one could immediately start typing the new search-term.
This should be a case for all the inputs around the editor (search, replace etc.), to have a little to quickly erase the input's content. !
I disagree, the user is going to be typing anyway, they can press backspace. In the search view at least you can still use the "clear search results" button to clear all the inputs whether results are present or not (in Insiders only)
This I agree with, I will keep the issue open to do this.
May I ask you why there is only a clear-search-option when no matched settings are found? Why can't we have it also when results are found? Feels kind of half-baked to me. Either there is an option available which enables to clear every search or there is no such option.
I don't want to clutter the UI by adding buttons for something that doesn't really need a button.
Why then not remove the clear-search-option completely? What purpose does it give in the case when no settings are found in contrast to when settings are found?
I guess that when no settings are found, you definitely want to clear the filter because there's nothing else to do, but when you are searching, you either found the setting you want or you want to tweak your search query to search for something different. When the page is full of settings, adding a button/link to clear the query would be UI noise.
I find myself often in one of the following situations when some settings for my typed search-term are found: Wrong settings are found because I didn't know the correct search-term and now I want to delete the complete term and type a completely knew one with the hope that the new term will show me the correct results. I typed the correct term and found the correct settings. After changing the settings I need to type a completely knew term because I want to search for the next settings which I want to change. I typed the correct term and found the correct settings. After changing the settings I want to come back to the default settings-view (where all settings are show as if you just opened the settings-UI). For this however I need first to select the entire search-term (double/triple click the term or select the term manually with the mouse) and then I need two press the del-button and afterwards move my hand back to the mouse. Instead one could simply click on a tiny del-icon right within the search-bar and instantly start typing the new term or even keep the hand on the mouse and keep searching trough the default-search-view. In fact I find the case when no results are found the most useless for a clear-search-button because when no settings are found I instantly can see that. In such a case my hands are usually still on the keyboard what means that it is easier to delete/correct the term with the keyboard instead of reaching to the mouse, clicking on the button and then again moving back to the keyboard to type the new-search-term.
Actually such a clear-search-button already exists in the keyboard-shortcuts-search-bar. You can see it in the screenshot on the far right within the search-bar. !
Got me there. I guess would take a PR that adds the same button to the settings editor.
I've been working on this issue.. Currently I have the search clear button working in the settings editor, I just need to tidy up placement as there is a search counter that appears where the action bar icons normally appear. I was thinking to just place the search counter that appears, slightly to the left beside where the clear button will be. What would you suggest for this?

this.countElement.style.borderColor = border; })); <del> this._register(this.searchWidget.onInputDidChange(() => this.onSearchInputChanged())); </del> <ins> this._register(this.searchWidget.onInputDidChange(() => { const searchVal = this.searchWidget.getValue(); clearInputAction.enabled = !!searchVal; this.onSearchInputChanged(); })); </ins> const headerControlsContainer = DOM.append(this.headerContainer, $('.settings-header-controls')); const targetWidgetContainer = DOM.append(headerControlsContainer, $('.settings-target-container')); this.settingsTargetsWidget = this._register(this.instantiationService.createInstance(SettingsTargetsWidget, targetWidgetContainer, { enableRemoteSettings: true })); this.settingsTargetsWidget.settingsTarget = ConfigurationTarget.USER_LOCAL; this.settingsTargetsWidget.onDidTargetChange(target => this.onDidSettingsTargetChange(target)); <ins> this.actionsContainer = DOM.append(searchContainer, DOM.$('.settings-clear-widget')); this.actionBar = this._register(new ActionBar(this.actionsContainer, { animated: false, actionViewItemProvider: (action: Action) => { return undefined; } })); this.actionBar.push([clearInputAction], { label: false, icon: true }); </ins> } private onDidSettingsTargetChange(target: SettingsTarget): void {


Question:
Issue Type: <bFeature Request</bThis new feature is over-eager and triggers on unsaved files that are not part of the commit, which I don't think makes sense. If I have staged file and am committing only file , I should not receive a warning that is unsaved. Ideally it will only consider staged files unless I am committing all staged and unstaged. VS Code version: Code 1.30.2 (, 2019-01-07T22:54:13.295Z) OS version: Windows_NT x64 10.0. <!-- generated by issue reporter --
Hi, can I work on this one?
Sure!
I'm not in favor of changing this. Or if it is changed, perhaps give finer grain control over when it prompts. I always want a prompt because I'm a bit lazy and usually let VSCode add the files to staging for me when I commit.
I see the value in your use case, but I don't think it makes sense in this feature. If you committed with a file that was untracked but saved this warning wouldn't help you. I think it would make more sense as a separate feature that warns on commit if there are untracked files regardless of save state.
Experienced this today. I had to loop on this experience 3 times before I finally groked what was occurring and my choices in the dialog. I believe there are two issues here: rules triggering the dialog dialog itself In my scenario today, this was triggered by me having an untracked file named open in VSCode. was previously saved to disk. It continues to be untracked. I had made some more changes to this file, but not yet saved those to disk. The key concern here for me is that this is an untracked file. I do not want to have any dialogs given to me by VSCode for untracked files when I attempt to commit. This is the dialog I was presented: I kept clicking cancel. Because I equated with . I wanted to answer to the question . On my 3rd time, I read again the dialog and every choice. I finally clicked and got the effect I desired. This dialog is poorly designed. The question proposed is a yes/no question "Would you like to save it before committing?". Unfortunately, the three buttons are not or . Instead they are answers to a question not asked...something like "What would you like to do now?". Naturally, that's a poor question and instead, this dialog needs to be reworked.
I've rephrased it to . Changed the to support for your use case.
, The text you proposed doesn't address the situation. Referencing the post I made, the file in question was unstaged. Therefore the text you propose doesn't address the unstaged files that are triggering this dialog box. You could change the text to but that's messy. Having two dialog boxes (one for unsaved staged, one for unsaved unstaged) is also messy. And one dialog box for each file is equally messy. All of this suggests to me that the feature itself needs rethinking, not just text in the dialog box. Personally (as a focus group of one), I don't want the feature. But someone somewhere though this feature was cool. So exploring with that group can perhaps surface a better mechanism to address their needs.
I see what you mean now. I simply removed the qualification for now. Thanks for the ping. I don't really think this small feature warrants such a big investment as a user study group, though.
One more small thing, the warning says But if the file has saved changes and also some unsaved changes, then the file will be included, it's just the unsaved changes that won't be included. This seems like it would be a common case so maybe it could say "will be incomplete in the commit" or "is unsaved and those changes will not be included" or "has unsaved changed that won't be included in the commit" something.
Changed to .

if (stagedUnsavedTextDocuments.length > 0) { const message = stagedUnsavedTextDocuments.length === 1 <del> ? localize('unsaved files single', "The following file is unsaved: {0}.nnWould you like to save it before committing?", path.basename(stagedUnsavedTextDocuments[0].uri.fsPath)) : localize('unsaved files', "There are {0} unsaved files.nnWould you like to save them before committing?", stagedUnsavedTextDocuments.length); </del> <ins> ? localize('unsaved files single', "The following staged file is unsaved: {0}.nnWould you like to save it before committing?", path.basename(stagedUnsavedTextDocuments[0].uri.fsPath)) : localize('unsaved files', "There are {0} unsaved staged files.nnWould you like to save them before committing?", stagedUnsavedTextDocuments.length); </ins> const saveAndCommit = localize('save and commit', "Save All & Commit"); const commit = localize('commit', "Commit Anyway"); const pick = await window.showWarningMessage(message, { modal: true }, saveAndCommit, commit);


Question: Issue Type: <bBug</bRepro steps: settings to for a setting screen really large :bug: Content does not center with the header <img width="1282" alt="image" src="https://user-"VS Code version: Code - Insiders 1.31.0-insider (, 2019-01-23T06:13:04.232Z) OS version: Darwin x64 18.2.0 <details<summarySystem Info</summary </details<details<summaryExtensions (6)</summaryExtensionVersion ------ vscode-browser-preview0.2.5 vscode-svgviewer1.4.7 prettier-vscode1.7.3 vscode-typescript-tslint-plugin0.3.0 debugger-for-chrome4.11.1 code-settings-sync3.2.4 (5 theme extensions excluded) </details<!-- generated by issue reporter --

text-decoration: underline; } <del> .settings-editor.no-toc-search > .settings-body .settings-tree-container .monaco-list-rows, </del> .settings-editor.narrow-width > .settings-body .settings-tree-container .monaco-list-rows { margin-left: 0px; }


Question:
VSCode Version: 1.31.0 OS Version: windows 10 Steps to Reproduce: the Help menu and select the release notes. any menu again click, right click, or select operation on this content page will not automatically close the open menu. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.502 --- <!-- score: 0.45 --<!-- potentialduplicatescomment --
Do not repeat with the above questions
Same root cause as I believe
Actually will keep open to make sure this is resolved by the fix

this._register(DOM.addDisposableListener(this.container, DOM.EventType.FOCUS_OUT, (e) => { let event = e as FocusEvent; <del> if (event.relatedTarget) { if (!this.container.contains(event.relatedTarget as HTMLElement)) { this.focusToReturn = undefined; this.setUnfocusedState(); } </del> <ins> if (!event.relatedTarget || !this.container.contains(event.relatedTarget as HTMLElement)) { this.focusToReturn = undefined; this.setUnfocusedState(); </ins> } }));


Question: Broken due to refactorings of the workbench CSS. Fix is simple (CSS only change).

cursor: pointer; } <del> .monaco-workbench .monaco-font-aliasing-antialiased { </del> <ins> .monaco-workbench.monaco-font-aliasing-antialiased { </ins> -webkit-font-smoothing: antialiased; } <del> .monaco-workbench .monaco-font-aliasing-none { </del> <ins> .monaco-workbench.monaco-font-aliasing-none { </ins> -webkit-font-smoothing: none; } @media (-webkit-min-device-pixel-ratio: 2), (min-resolution: 192dpi) { <del> .monaco-workbench .monaco-font-aliasing-auto { </del> <ins> .monaco-workbench.monaco-font-aliasing-auto { </ins> -webkit-font-smoothing: antialiased; } }


Question:
I do not see a duplicate of my issue: ! So I'm in the clear. <!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.32.0 OS Version: Windows 10 1809 Stable Steps to Reproduce: Visual Studio Code, click on the "Search" sidebar menu item to bring up the huge Search menu. ! for a common word used quite a lot. Like "a", "let", "var", "i", and so forth. the Search displays the total results count, dismiss a few of them. total results count should decrement by 1 per dismissal, or indicate both the original total results count and the remaining non-dismissed total results count side by side when dismissing the search results. For example: ! Does this issue occur when all extensions are disabled?: Yes
For me, it does decrement. You don't see that? You are clicking the 'x' icon on a result row, right?
It doesn't. !
Ok, so I was about to get it to decrement, but that's not done in real-time. ! Both of the GIFs are done in 1.32.1.
That's right, I thought you were talking about the total shown at the top ("x results in y files") in your original post.
This also happens when a new match is or deleted in an existing file match. !

return; } <del> const root = element instanceof SearchResult ? null : element; this.tree.setChildren(root, this.createIterator(element, collapseResults)); </del> <ins> if (element instanceof SearchResult) { this.tree.setChildren(null, this.createIterator(element, collapseResults)); } else { this.tree.setChildren(element, this.createIterator(element, collapseResults)); this.tree.rerender(element); } </ins> }); } }


Question:
Issue Type: <bBug</bSee also - but note that people say they Debug console behaves normally Debug console scrolls to top after each evaluated line this code as breakpoints at "Uncaught exceptions" in VS Code hitting SystemExit exception, run in Debug console. a bunch of times (1-5 times) in the Debug console. that at one point, Debug console scrolls to top to bottom of Debug console output in Debug console. that you don't see due to Debug console scrolling near top again. VS Code version: Code 1.32.1 (, 2019-03-08T00:51:49.278Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (5)</summaryExtensionVersion ------ latex-workshop6.2.0 svn-scm1.47.1 python2019.2.5558 multi-command1.3.0 code-settings-sync3.2.7 </details<!-- generated by issue reporter --
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.628 --- <!-- score: 0.584 --- <!-- score: 0.578 --- <!-- score: 0.544 --- <!-- score: 0.502 --<!-- potentialduplicatescomment --
Yes, looks like is a duplicate of this one, although does not have specific reproduction steps. This one does. Also, it looks like they investigated 1.32.0-insider, while I am still seeing this in 1.32.1. Also, I can repro this in the latest insider build with only the Python extension and no settings changed whatsoever (see below). Finally, I must admit finding repro steps was a bit difficult. So I am not fully convinced this issue is fixed, as implied by .
I can not reproduce this. Can you attach a gif / video showing this can you repro this using python?
Sure, here's a GIF: !
I can not reproduce with node. please try reproducing with python if you F1 developer tools put a breakpoint what do you see as scrollTop, scrollHeight and renderHeight at the exact moment when the debug console scrolls unexpectedly?
I encountered exactly the same issue as
then you can also try to answer the quesionts i asked . Get your hands dirty and do some debugging. Thanks
Breakpoint is hit twice per manual . After the first time manually entering , with the breakpoint hit at line 85: scrollTop = 0, scrollHeight = 19, renderHeight = 214 scrollTop = 0, scrollHeight = 480, renderHeight = 214 After the second time manually entering : scrollTop = 266, scrollHeight = 480, renderHeight = 214 scrollTop = 266, scrollHeight = 80, renderHeight = 214 (+) After (+), debug console is scrolled to top. I noticed that during (+), the debug console is empty, but not during any of the other breakpoint hits. I double-checked: is not a typo of , the above numbers are correct.
Yes, I too can replicate this issue on my Mac
Ok, thanks for help everybody. I can repro on my mac. Investigating...
After investigating and discussion with we figured out it is a dup of
Version: 1.34.0-insider Commit: Date: 2019-04-19T19:59:19.092Z Electron: 3.1.8 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Darwin x64 18.2.0 This issue is not fixed in latest Insider and bugs me every day: !
I'm facing this since few months now. Any clue on how to avoid this issue? Please do not keep on closing this issue as it is real.
Check the insider release and see if it's fixed for you (it was for me). It seems the maintainers have chosen to leave this broken for everyone until their next major release next month which is unfortunate.
I'm on Insiders, it's not fixed for me.. Version: 1.34.0-insider Commit: Date: 2019-04-19T19:59:19.092Z Electron: 3.1.8 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Darwin x64 18.2.0
I have the same issue. Version: 1.33.1 Commit: Date: 2019-04-11T08:20:22.771Z Electron: 3.1.6 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Linux x64 4.15.0-34-generic snap
I'm having this issue even on the latest Insiders version (1.34.20-insider) See gif here :
Same issue here. Version: 1.33.1 (system setup) Commit: Date: 2019-04-11T08:27:09.080Z Electron: 3.1.6 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Windows_NT ia32 10.0.
please do not close this issue. I am experiencing same problem: VSCode version: 1.33.1 System Software Overview: System Version: macOS 10.14.4 (18E226) Kernel Version: Darwin 18.5.0 Boot Volume: Mac OS Boot Mode: Normal Computer Name: iMac001 Secure Virtual Memory: Enabled System Integrity Protection: Enabled Time since boot: 7 days 6 minutes
sorry that this is a pain. I am looking into it but can not reproduce. Can you provide exact steps please?
Hi OP here. I can still repro the bug in official 1.34.0, so this is certainly not fixed. However, my repro steps from the original description do not work any longer as running actually ends the process that is debugged. I managed to repro the same issue with . So these are my current repro steps: this code as in VS Code hitting the breakpoint, run in Debug console. a bunch of times (1-5 times) in the Debug console. that at one point, Debug console scrolls up quite a bit to bottom of Debug console output in Debug console. that you don't see due to Debug console scrolling near top again. Here's a gif as well. (The gif misses step 6, but I think it gets the main issue across.) !
Thanks for the steps, I will look into this this or next week.
we have pushed a fix with the help of Please try it with VSCode insiders starting from Tuesday which will have the fix. Thank you
I have just checked and it seems to me the issue is gone, thank you! (Of course, I will be more confident once an actual release has the fix as I haven't re-setup insiders the exact same way I use my release version - let's hope for the best!)
Thanks. Adding verified label. Let us know how it goes once you get the stable update.
Stable looks good to me, too, thanks!

layout(dimension: dom.Dimension): void { this.dimension = dimension; if (this.tree) { <ins> const lastElementVisible = this.tree.scrollTop + this.tree.renderHeight >= this.tree.scrollHeight; </ins> const treeHeight = dimension.height - this.replInputHeight; this.tree.getHTMLElement().style.height = `${treeHeight}px`; this.tree.layout(treeHeight, dimension.width); <ins> if (lastElementVisible) { revealLastElement(this.tree); } </ins> } this.replInputContainer.style.height = `${this.replInputHeight}px`;


Question:
Issue Type: <bBug</bSee also - but note that people say they Debug console behaves normally Debug console scrolls to top after each evaluated line this code as breakpoints at "Uncaught exceptions" in VS Code hitting SystemExit exception, run in Debug console. a bunch of times (1-5 times) in the Debug console. that at one point, Debug console scrolls to top to bottom of Debug console output in Debug console. that you don't see due to Debug console scrolling near top again. VS Code version: Code 1.32.1 (, 2019-03-08T00:51:49.278Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (5)</summaryExtensionVersion ------ latex-workshop6.2.0 svn-scm1.47.1 python2019.2.5558 multi-command1.3.0 code-settings-sync3.2.7 </details<!-- generated by issue reporter --
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.628 --- <!-- score: 0.584 --- <!-- score: 0.578 --- <!-- score: 0.544 --- <!-- score: 0.502 --<!-- potentialduplicatescomment --
Yes, looks like is a duplicate of this one, although does not have specific reproduction steps. This one does. Also, it looks like they investigated 1.32.0-insider, while I am still seeing this in 1.32.1. Also, I can repro this in the latest insider build with only the Python extension and no settings changed whatsoever (see below). Finally, I must admit finding repro steps was a bit difficult. So I am not fully convinced this issue is fixed, as implied by .
I can not reproduce this. Can you attach a gif / video showing this can you repro this using python?
Sure, here's a GIF: !
I can not reproduce with node. please try reproducing with python if you F1 developer tools put a breakpoint what do you see as scrollTop, scrollHeight and renderHeight at the exact moment when the debug console scrolls unexpectedly?
I encountered exactly the same issue as
then you can also try to answer the quesionts i asked . Get your hands dirty and do some debugging. Thanks
Breakpoint is hit twice per manual . After the first time manually entering , with the breakpoint hit at line 85: scrollTop = 0, scrollHeight = 19, renderHeight = 214 scrollTop = 0, scrollHeight = 480, renderHeight = 214 After the second time manually entering : scrollTop = 266, scrollHeight = 480, renderHeight = 214 scrollTop = 266, scrollHeight = 80, renderHeight = 214 (+) After (+), debug console is scrolled to top. I noticed that during (+), the debug console is empty, but not during any of the other breakpoint hits. I double-checked: is not a typo of , the above numbers are correct.
Yes, I too can replicate this issue on my Mac
Ok, thanks for help everybody. I can repro on my mac. Investigating...
After investigating and discussion with we figured out it is a dup of
Version: 1.34.0-insider Commit: Date: 2019-04-19T19:59:19.092Z Electron: 3.1.8 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Darwin x64 18.2.0 This issue is not fixed in latest Insider and bugs me every day: !
I'm facing this since few months now. Any clue on how to avoid this issue? Please do not keep on closing this issue as it is real.
Check the insider release and see if it's fixed for you (it was for me). It seems the maintainers have chosen to leave this broken for everyone until their next major release next month which is unfortunate.
I'm on Insiders, it's not fixed for me.. Version: 1.34.0-insider Commit: Date: 2019-04-19T19:59:19.092Z Electron: 3.1.8 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Darwin x64 18.2.0
I have the same issue. Version: 1.33.1 Commit: Date: 2019-04-11T08:20:22.771Z Electron: 3.1.6 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Linux x64 4.15.0-34-generic snap
I'm having this issue even on the latest Insiders version (1.34.20-insider) See gif here :
Same issue here. Version: 1.33.1 (system setup) Commit: Date: 2019-04-11T08:27:09.080Z Electron: 3.1.6 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Windows_NT ia32 10.0.
please do not close this issue. I am experiencing same problem: VSCode version: 1.33.1 System Software Overview: System Version: macOS 10.14.4 (18E226) Kernel Version: Darwin 18.5.0 Boot Volume: Mac OS Boot Mode: Normal Computer Name: iMac001 Secure Virtual Memory: Enabled System Integrity Protection: Enabled Time since boot: 7 days 6 minutes
sorry that this is a pain. I am looking into it but can not reproduce. Can you provide exact steps please?
Hi OP here. I can still repro the bug in official 1.34.0, so this is certainly not fixed. However, my repro steps from the original description do not work any longer as running actually ends the process that is debugged. I managed to repro the same issue with . So these are my current repro steps: this code as in VS Code hitting the breakpoint, run in Debug console. a bunch of times (1-5 times) in the Debug console. that at one point, Debug console scrolls up quite a bit to bottom of Debug console output in Debug console. that you don't see due to Debug console scrolling near top again. Here's a gif as well. (The gif misses step 6, but I think it gets the main issue across.) !
Thanks for the steps, I will look into this this or next week.
we have pushed a fix with the help of Please try it with VSCode insiders starting from Tuesday which will have the fix. Thank you
I have just checked and it seems to me the issue is gone, thank you! (Of course, I will be more confident once an actual release has the fix as I haven't re-setup insiders the exact same way I use my release version - let's hope for the best!)
Thanks. Adding verified label. Let us know how it goes once you get the stable update.
Stable looks good to me, too, thanks!

if (this.replElementsChangeListener) { this.replElementsChangeListener.dispose(); } <ins> this.refreshScheduler.dispose(); </ins> super.dispose(); } }


Question:
Issue Type: <bBug</bSee also - but note that people say they Debug console behaves normally Debug console scrolls to top after each evaluated line this code as breakpoints at "Uncaught exceptions" in VS Code hitting SystemExit exception, run in Debug console. a bunch of times (1-5 times) in the Debug console. that at one point, Debug console scrolls to top to bottom of Debug console output in Debug console. that you don't see due to Debug console scrolling near top again. VS Code version: Code 1.32.1 (, 2019-03-08T00:51:49.278Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (5)</summaryExtensionVersion ------ latex-workshop6.2.0 svn-scm1.47.1 python2019.2.5558 multi-command1.3.0 code-settings-sync3.2.7 </details<!-- generated by issue reporter --
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.628 --- <!-- score: 0.584 --- <!-- score: 0.578 --- <!-- score: 0.544 --- <!-- score: 0.502 --<!-- potentialduplicatescomment --
Yes, looks like is a duplicate of this one, although does not have specific reproduction steps. This one does. Also, it looks like they investigated 1.32.0-insider, while I am still seeing this in 1.32.1. Also, I can repro this in the latest insider build with only the Python extension and no settings changed whatsoever (see below). Finally, I must admit finding repro steps was a bit difficult. So I am not fully convinced this issue is fixed, as implied by .
I can not reproduce this. Can you attach a gif / video showing this can you repro this using python?
Sure, here's a GIF: !
I can not reproduce with node. please try reproducing with python if you F1 developer tools put a breakpoint what do you see as scrollTop, scrollHeight and renderHeight at the exact moment when the debug console scrolls unexpectedly?
I encountered exactly the same issue as
then you can also try to answer the quesionts i asked . Get your hands dirty and do some debugging. Thanks
Breakpoint is hit twice per manual . After the first time manually entering , with the breakpoint hit at line 85: scrollTop = 0, scrollHeight = 19, renderHeight = 214 scrollTop = 0, scrollHeight = 480, renderHeight = 214 After the second time manually entering : scrollTop = 266, scrollHeight = 480, renderHeight = 214 scrollTop = 266, scrollHeight = 80, renderHeight = 214 (+) After (+), debug console is scrolled to top. I noticed that during (+), the debug console is empty, but not during any of the other breakpoint hits. I double-checked: is not a typo of , the above numbers are correct.
Yes, I too can replicate this issue on my Mac
Ok, thanks for help everybody. I can repro on my mac. Investigating...
After investigating and discussion with we figured out it is a dup of
Version: 1.34.0-insider Commit: Date: 2019-04-19T19:59:19.092Z Electron: 3.1.8 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Darwin x64 18.2.0 This issue is not fixed in latest Insider and bugs me every day: !
I'm facing this since few months now. Any clue on how to avoid this issue? Please do not keep on closing this issue as it is real.
Check the insider release and see if it's fixed for you (it was for me). It seems the maintainers have chosen to leave this broken for everyone until their next major release next month which is unfortunate.
I'm on Insiders, it's not fixed for me.. Version: 1.34.0-insider Commit: Date: 2019-04-19T19:59:19.092Z Electron: 3.1.8 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Darwin x64 18.2.0
I have the same issue. Version: 1.33.1 Commit: Date: 2019-04-11T08:20:22.771Z Electron: 3.1.6 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Linux x64 4.15.0-34-generic snap
I'm having this issue even on the latest Insiders version (1.34.20-insider) See gif here :
Same issue here. Version: 1.33.1 (system setup) Commit: Date: 2019-04-11T08:27:09.080Z Electron: 3.1.6 Chrome: 66.0.3359.181 10.2.0 V8: 6.6.346.32 OS: Windows_NT ia32 10.0.
please do not close this issue. I am experiencing same problem: VSCode version: 1.33.1 System Software Overview: System Version: macOS 10.14.4 (18E226) Kernel Version: Darwin 18.5.0 Boot Volume: Mac OS Boot Mode: Normal Computer Name: iMac001 Secure Virtual Memory: Enabled System Integrity Protection: Enabled Time since boot: 7 days 6 minutes
sorry that this is a pain. I am looking into it but can not reproduce. Can you provide exact steps please?
Hi OP here. I can still repro the bug in official 1.34.0, so this is certainly not fixed. However, my repro steps from the original description do not work any longer as running actually ends the process that is debugged. I managed to repro the same issue with . So these are my current repro steps: this code as in VS Code hitting the breakpoint, run in Debug console. a bunch of times (1-5 times) in the Debug console. that at one point, Debug console scrolls up quite a bit to bottom of Debug console output in Debug console. that you don't see due to Debug console scrolling near top again. Here's a gif as well. (The gif misses step 6, but I think it gets the main issue across.) !
Thanks for the steps, I will look into this this or next week.
we have pushed a fix with the help of Please try it with VSCode insiders starting from Tuesday which will have the fix. Thank you
I have just checked and it seems to me the issue is gone, thank you! (Of course, I will be more confident once an actual release has the fix as I haven't re-setup insiders the exact same way I use my release version - let's hope for the best!)
Thanks. Adding verified label. Let us know how it goes once you get the stable update.
Stable looks good to me, too, thanks!

constructor(private configurationService: IConfigurationService) { } getHeight(element: IReplElement): number { <ins> const countNumberOfLines = (str: string) => Math.max(1, (str.match(/rn|n/g) || []).length); </ins> // Give approximate heights. Repl has dynamic height so the tree will measure the actual height on its own. const fontSize = this.configurationService.getValue<IDebugConfiguration>('debug').console.fontSize; const rowHeight = Math.ceil(1.4 * fontSize); <del> if (element instanceof Expression && element.hasChildren) { return 2 * rowHeight; } </del> // In order to keep scroll position we need to give a good approximation to the tree <del> if (element instanceof SimpleReplElement) { // For every 150 characters increase the number of lines needed let count = Math.ceil(element.value.length / 150); for (let i = 0; i < element.value.length; i++) { if (element.value[i] === 'n' || element.value[i] === 'rn') { count++; } </del> <ins> // For every 150 characters increase the number of lines needed if (element instanceof Expression) { let { name, value } = element; let nameRows = countNumberOfLines(name) + Math.floor(name.length / 150); if (element.hasChildren) { return (nameRows + 1) * rowHeight; </ins> } <del> return Math.max(1, count) * rowHeight; </del> <ins> let valueRows = countNumberOfLines(value) + Math.floor(value.length / 150); return rowHeight * (nameRows + valueRows); } if (element instanceof SimpleReplElement) { let value = element.value; let valueRows = countNumberOfLines(value) + Math.floor(value.length / 150); return valueRows * rowHeight; </ins> } return rowHeight;


Question:
Hi, I am a bit new, and I have a simple code example on VS Code v1.32.3. It says I have an error, ok fine..... but then when I chose the "Quick Fix" option there is never a Quick Fix for this or any other thing in the past I tried to do a quick fix on. Whats the point of having a Quick Fix feature, if it doesn't do anything ? Im a bit confused. . This is the code I tried to do a quick fix on (its an extremely simple code): . ! When I try to fix, I get this: . !
I also get this issue for Python but seems to apply to any language. I have the Python extension as well as Intellicode. Still a current issue with 1.33 (Insiders) with the latest update.
Quick Fix... action is shown even when there are no quick fixes (code actions) available. May be it can hidden then.
Optimally, an actual corrective action would be taken (or at least suggested) based on the feedback provided by the language extensions (Python and Intellicode for my use-case).
Same here, I always get the "No code actions available" when I try to Quick Fix my code, no matter the language used, and even if I have no extension installed. ! ! I do not really know why it is not working, but I can't get to remember since when this bug is occurring to me ( I remember last summer it was okay, and I think during December too while I was working on an Angular Project )
Our C/C++ extensions does have lightbulb code actions for the error squiggle, but the quick fix still says "no code action" available -- is that a bug? Let us know if our extension isn't doing something correctly. I didn't understand the docs at . ! !
Can you please provide simple steps to repro this?
It occurs when you have a .c or .cpp file with text . We report the squiggle message via textDocumentpublishDiagnostics and the code action from textDocumentcodeAction. Do we need to do something special to associate the code action with the squiggle's QuickFix?
Quick Fix action asks for all code actions in that diagnostic range and of kind . What kind are your quick fix code actions?
Okay thanks a lot for informing us -- the "CodeActionKind" type is completely new to us. Our code action just returns a Command and not the additional info like the CodeActionKind. I filed a work item for us at . We have a lot of "catching up" to do with the LSP updates.
I have had this issue for weeks with C#, and I finally figured out that it was just the menu. Basic stuff where it used to suggest "using System;" no longer showed up. After reading this issue, I tried the command and the keyboard shortcut works but not the menu. This image shows what happens when clicking the "Quick fix..." menu: <img width="387" alt="screenshot from menu" src="https://user-"And this is what shows when pressing : <img width="414" alt="screenshot from keyboard" src="https://user-"This looks similar to the screenshots from and .
Seriously kills productivity, I am reinstalling PyCharm
Looks like C# extension is also not using the code action kind for their code actions. Probably we have to show all code actions for the given range.
I see the same issue with JSHint/JavaScript. ! !
The same thing (No code actions available) with PowerShell.
Same issue with TypeScript in .tsx file. ! !
This has been nearly two months! any fixes for this ? I'm having this issue in the latest version as well(Python)!
This feature becomes very important when you're upgrading code from a legacy version (such as Python 2) to the updated version (Python 3). I'm sure there are other languages have similar stipulations such as converting C to C++ or C# or vice versa (or even C# to C++ and vice versa).
I also have this issue, and this is very important when create the new project, but the works for me!
I also had this issue and only learned today from some searching that (on Linux) brings up the quick fix list of actual working suggestions EDIT: As shows below, that's the same issue I find when hovering using C#
This doesn't seem to be a problem for C# in my case atm (I'm using Unity/Mono). I exclusively use though.
I get the same with Powershell. ! ! However selecting it and press ctrl+. gave me the suggestion !
On a Mac, the Quick Fix shortcut appears to be ⌘. (Command + Period). It would be super helpful if we could get the quick fix to appear on mouse hover, though!
Hello there, I have the same problem since today. Quick fix was working a week ago but now clicking on "quick fix" and then clicking on suggestion do nothing. But if I use ctrl+; to show suggestion it work.
Just to clarify what was fixed by : we now only show the button in the hover if we know for sure that that quick fixes are available. A few extensions provide quick fix style code action but do not explicitly mark them as quick fixes. Those code actions will show up in the lightbulb menu but not if you click in errors hovers (because we only want to show code actions that we know for sure will fix something). Extensions must mark their quick fix code actions as  to have them show up in the problem hover menu too
can you verify that the python extension is good in this regard?
I took a look at my installed extensions and noticed the C# extension was complaining that it needed to be reloaded. Hmm, so check your extensions list first. This is what I was presented after clicking reload. Notice the version I'm running as of today's date stamp after I reloaded the C# extension. I hope this helps some of you. ! ! ! Be sure to click on the instance first, then use ctrl+. for windows ! You should now see the using statement, for example like on line 1 !

this._ui.update(newState); } <del> public showCodeActions(actions: Promise<CodeActionSet>, at: IAnchor | IPosition) { </del> <ins> public showCodeActions(actions: CodeActionSet, at: IAnchor | IPosition) { </ins> return this._ui.showCodeActionList(actions, at); }


Question:
Hi, I am a bit new, and I have a simple code example on VS Code v1.32.3. It says I have an error, ok fine..... but then when I chose the "Quick Fix" option there is never a Quick Fix for this or any other thing in the past I tried to do a quick fix on. Whats the point of having a Quick Fix feature, if it doesn't do anything ? Im a bit confused. . This is the code I tried to do a quick fix on (its an extremely simple code): . ! When I try to fix, I get this: . !
I also get this issue for Python but seems to apply to any language. I have the Python extension as well as Intellicode. Still a current issue with 1.33 (Insiders) with the latest update.
Quick Fix... action is shown even when there are no quick fixes (code actions) available. May be it can hidden then.
Optimally, an actual corrective action would be taken (or at least suggested) based on the feedback provided by the language extensions (Python and Intellicode for my use-case).
Same here, I always get the "No code actions available" when I try to Quick Fix my code, no matter the language used, and even if I have no extension installed. ! ! I do not really know why it is not working, but I can't get to remember since when this bug is occurring to me ( I remember last summer it was okay, and I think during December too while I was working on an Angular Project )
Our C/C++ extensions does have lightbulb code actions for the error squiggle, but the quick fix still says "no code action" available -- is that a bug? Let us know if our extension isn't doing something correctly. I didn't understand the docs at . ! !
Can you please provide simple steps to repro this?
It occurs when you have a .c or .cpp file with text . We report the squiggle message via textDocumentpublishDiagnostics and the code action from textDocumentcodeAction. Do we need to do something special to associate the code action with the squiggle's QuickFix?
Quick Fix action asks for all code actions in that diagnostic range and of kind . What kind are your quick fix code actions?
Okay thanks a lot for informing us -- the "CodeActionKind" type is completely new to us. Our code action just returns a Command and not the additional info like the CodeActionKind. I filed a work item for us at . We have a lot of "catching up" to do with the LSP updates.
I have had this issue for weeks with C#, and I finally figured out that it was just the menu. Basic stuff where it used to suggest "using System;" no longer showed up. After reading this issue, I tried the command and the keyboard shortcut works but not the menu. This image shows what happens when clicking the "Quick fix..." menu: <img width="387" alt="screenshot from menu" src="https://user-"And this is what shows when pressing : <img width="414" alt="screenshot from keyboard" src="https://user-"This looks similar to the screenshots from and .
Seriously kills productivity, I am reinstalling PyCharm
Looks like C# extension is also not using the code action kind for their code actions. Probably we have to show all code actions for the given range.
I see the same issue with JSHint/JavaScript. ! !
The same thing (No code actions available) with PowerShell.
Same issue with TypeScript in .tsx file. ! !
This has been nearly two months! any fixes for this ? I'm having this issue in the latest version as well(Python)!
This feature becomes very important when you're upgrading code from a legacy version (such as Python 2) to the updated version (Python 3). I'm sure there are other languages have similar stipulations such as converting C to C++ or C# or vice versa (or even C# to C++ and vice versa).
I also have this issue, and this is very important when create the new project, but the works for me!
I also had this issue and only learned today from some searching that (on Linux) brings up the quick fix list of actual working suggestions EDIT: As shows below, that's the same issue I find when hovering using C#
This doesn't seem to be a problem for C# in my case atm (I'm using Unity/Mono). I exclusively use though.
I get the same with Powershell. ! ! However selecting it and press ctrl+. gave me the suggestion !
On a Mac, the Quick Fix shortcut appears to be ⌘. (Command + Period). It would be super helpful if we could get the quick fix to appear on mouse hover, though!
Hello there, I have the same problem since today. Quick fix was working a week ago but now clicking on "quick fix" and then clicking on suggestion do nothing. But if I use ctrl+; to show suggestion it work.
Just to clarify what was fixed by : we now only show the button in the hover if we know for sure that that quick fixes are available. A few extensions provide quick fix style code action but do not explicitly mark them as quick fixes. Those code actions will show up in the lightbulb menu but not if you click in errors hovers (because we only want to show code actions that we know for sure will fix something). Extensions must mark their quick fix code actions as  to have them show up in the problem hover menu too
can you verify that the python extension is good in this regard?
I took a look at my installed extensions and noticed the C# extension was complaining that it needed to be reloaded. Hmm, so check your extensions list first. This is what I was presented after clicking reload. Notice the version I'm running as of today's date stamp after I reloaded the C# extension. I hope this helps some of you. ! ! ! Be sure to click on the instance first, then use ctrl+. for windows ! You should now see the using statement, for example like on line 1 !

} } <del> public async showCodeActionList(codeActions: Promise<CodeActionSet>, at?: IAnchor | IPosition): Promise<void> { let actions: CodeActionSet; try { actions = await codeActions; } catch (e) { onUnexpectedError(e); return; } </del> <ins> public async showCodeActionList(actions: CodeActionSet, at?: IAnchor | IPosition): Promise<void> { </ins> this._codeActionWidget.show(actions, at); }


Question:
Hi, I am a bit new, and I have a simple code example on VS Code v1.32.3. It says I have an error, ok fine..... but then when I chose the "Quick Fix" option there is never a Quick Fix for this or any other thing in the past I tried to do a quick fix on. Whats the point of having a Quick Fix feature, if it doesn't do anything ? Im a bit confused. . This is the code I tried to do a quick fix on (its an extremely simple code): . ! When I try to fix, I get this: . !
I also get this issue for Python but seems to apply to any language. I have the Python extension as well as Intellicode. Still a current issue with 1.33 (Insiders) with the latest update.
Quick Fix... action is shown even when there are no quick fixes (code actions) available. May be it can hidden then.
Optimally, an actual corrective action would be taken (or at least suggested) based on the feedback provided by the language extensions (Python and Intellicode for my use-case).
Same here, I always get the "No code actions available" when I try to Quick Fix my code, no matter the language used, and even if I have no extension installed. ! ! I do not really know why it is not working, but I can't get to remember since when this bug is occurring to me ( I remember last summer it was okay, and I think during December too while I was working on an Angular Project )
Our C/C++ extensions does have lightbulb code actions for the error squiggle, but the quick fix still says "no code action" available -- is that a bug? Let us know if our extension isn't doing something correctly. I didn't understand the docs at . ! !
Can you please provide simple steps to repro this?
It occurs when you have a .c or .cpp file with text . We report the squiggle message via textDocumentpublishDiagnostics and the code action from textDocumentcodeAction. Do we need to do something special to associate the code action with the squiggle's QuickFix?
Quick Fix action asks for all code actions in that diagnostic range and of kind . What kind are your quick fix code actions?
Okay thanks a lot for informing us -- the "CodeActionKind" type is completely new to us. Our code action just returns a Command and not the additional info like the CodeActionKind. I filed a work item for us at . We have a lot of "catching up" to do with the LSP updates.
I have had this issue for weeks with C#, and I finally figured out that it was just the menu. Basic stuff where it used to suggest "using System;" no longer showed up. After reading this issue, I tried the command and the keyboard shortcut works but not the menu. This image shows what happens when clicking the "Quick fix..." menu: <img width="387" alt="screenshot from menu" src="https://user-"And this is what shows when pressing : <img width="414" alt="screenshot from keyboard" src="https://user-"This looks similar to the screenshots from and .
Seriously kills productivity, I am reinstalling PyCharm
Looks like C# extension is also not using the code action kind for their code actions. Probably we have to show all code actions for the given range.
I see the same issue with JSHint/JavaScript. ! !
The same thing (No code actions available) with PowerShell.
Same issue with TypeScript in .tsx file. ! !
This has been nearly two months! any fixes for this ? I'm having this issue in the latest version as well(Python)!
This feature becomes very important when you're upgrading code from a legacy version (such as Python 2) to the updated version (Python 3). I'm sure there are other languages have similar stipulations such as converting C to C++ or C# or vice versa (or even C# to C++ and vice versa).
I also have this issue, and this is very important when create the new project, but the works for me!
I also had this issue and only learned today from some searching that (on Linux) brings up the quick fix list of actual working suggestions EDIT: As shows below, that's the same issue I find when hovering using C#
This doesn't seem to be a problem for C# in my case atm (I'm using Unity/Mono). I exclusively use though.
I get the same with Powershell. ! ! However selecting it and press ctrl+. gave me the suggestion !
On a Mac, the Quick Fix shortcut appears to be ⌘. (Command + Period). It would be super helpful if we could get the quick fix to appear on mouse hover, though!
Hello there, I have the same problem since today. Quick fix was working a week ago but now clicking on "quick fix" and then clicking on suggestion do nothing. But if I use ctrl+; to show suggestion it work.
Just to clarify what was fixed by : we now only show the button in the hover if we know for sure that that quick fixes are available. A few extensions provide quick fix style code action but do not explicitly mark them as quick fixes. Those code actions will show up in the lightbulb menu but not if you click in errors hovers (because we only want to show code actions that we know for sure will fix something). Extensions must mark their quick fix code actions as  to have them show up in the problem hover menu too
can you verify that the python extension is good in this regard?
I took a look at my installed extensions and noticed the C# extension was complaining that it needed to be reloaded. Hmm, so check your extensions list first. This is what I was presented after clicking reload. Notice the version I'm running as of today's date stamp after I reloaded the C# extension. I hope this helps some of you. ! ! ! Be sure to click on the instance first, then use ctrl+. for windows ! You should now see the using statement, for example like on line 1 !

import { Position } from 'vs/editor/common/core/position'; import { IRange, Range } from 'vs/editor/common/core/range'; import { ModelDecorationOptions } from 'vs/editor/common/model/textModel'; <del> import { DocumentColorProvider, Hover as MarkdownHover, HoverProviderRegistry, IColor, CodeAction } from 'vs/editor/common/modes'; </del> <ins> import { DocumentColorProvider, Hover as MarkdownHover, HoverProviderRegistry, IColor } from 'vs/editor/common/modes'; </ins> import { getColorPresentations } from 'vs/editor/contrib/colorPicker/color'; import { ColorDetector } from 'vs/editor/contrib/colorPicker/colorDetector'; import { ColorPickerModel } from 'vs/editor/contrib/colorPicker/colorPickerModel';


Question:
Hi, I am a bit new, and I have a simple code example on VS Code v1.32.3. It says I have an error, ok fine..... but then when I chose the "Quick Fix" option there is never a Quick Fix for this or any other thing in the past I tried to do a quick fix on. Whats the point of having a Quick Fix feature, if it doesn't do anything ? Im a bit confused. . This is the code I tried to do a quick fix on (its an extremely simple code): . ! When I try to fix, I get this: . !
I also get this issue for Python but seems to apply to any language. I have the Python extension as well as Intellicode. Still a current issue with 1.33 (Insiders) with the latest update.
Quick Fix... action is shown even when there are no quick fixes (code actions) available. May be it can hidden then.
Optimally, an actual corrective action would be taken (or at least suggested) based on the feedback provided by the language extensions (Python and Intellicode for my use-case).
Same here, I always get the "No code actions available" when I try to Quick Fix my code, no matter the language used, and even if I have no extension installed. ! ! I do not really know why it is not working, but I can't get to remember since when this bug is occurring to me ( I remember last summer it was okay, and I think during December too while I was working on an Angular Project )
Our C/C++ extensions does have lightbulb code actions for the error squiggle, but the quick fix still says "no code action" available -- is that a bug? Let us know if our extension isn't doing something correctly. I didn't understand the docs at . ! !
Can you please provide simple steps to repro this?
It occurs when you have a .c or .cpp file with text . We report the squiggle message via textDocumentpublishDiagnostics and the code action from textDocumentcodeAction. Do we need to do something special to associate the code action with the squiggle's QuickFix?
Quick Fix action asks for all code actions in that diagnostic range and of kind . What kind are your quick fix code actions?
Okay thanks a lot for informing us -- the "CodeActionKind" type is completely new to us. Our code action just returns a Command and not the additional info like the CodeActionKind. I filed a work item for us at . We have a lot of "catching up" to do with the LSP updates.
I have had this issue for weeks with C#, and I finally figured out that it was just the menu. Basic stuff where it used to suggest "using System;" no longer showed up. After reading this issue, I tried the command and the keyboard shortcut works but not the menu. This image shows what happens when clicking the "Quick fix..." menu: <img width="387" alt="screenshot from menu" src="https://user-"And this is what shows when pressing : <img width="414" alt="screenshot from keyboard" src="https://user-"This looks similar to the screenshots from and .
Seriously kills productivity, I am reinstalling PyCharm
Looks like C# extension is also not using the code action kind for their code actions. Probably we have to show all code actions for the given range.
I see the same issue with JSHint/JavaScript. ! !
The same thing (No code actions available) with PowerShell.
Same issue with TypeScript in .tsx file. ! !
This has been nearly two months! any fixes for this ? I'm having this issue in the latest version as well(Python)!
This feature becomes very important when you're upgrading code from a legacy version (such as Python 2) to the updated version (Python 3). I'm sure there are other languages have similar stipulations such as converting C to C++ or C# or vice versa (or even C# to C++ and vice versa).
I also have this issue, and this is very important when create the new project, but the works for me!
I also had this issue and only learned today from some searching that (on Linux) brings up the quick fix list of actual working suggestions EDIT: As shows below, that's the same issue I find when hovering using C#
This doesn't seem to be a problem for C# in my case atm (I'm using Unity/Mono). I exclusively use though.
I get the same with Powershell. ! ! However selecting it and press ctrl+. gave me the suggestion !
On a Mac, the Quick Fix shortcut appears to be ⌘. (Command + Period). It would be super helpful if we could get the quick fix to appear on mouse hover, though!
Hello there, I have the same problem since today. Quick fix was working a week ago but now clicking on "quick fix" and then clicking on suggestion do nothing. But if I use ctrl+; to show suggestion it work.
Just to clarify what was fixed by : we now only show the button in the hover if we know for sure that that quick fixes are available. A few extensions provide quick fix style code action but do not explicitly mark them as quick fixes. Those code actions will show up in the lightbulb menu but not if you click in errors hovers (because we only want to show code actions that we know for sure will fix something). Extensions must mark their quick fix code actions as  to have them show up in the problem hover menu too
can you verify that the python extension is good in this regard?
I took a look at my installed extensions and noticed the C# extension was complaining that it needed to be reloaded. Hmm, so check your extensions list first. This is what I was presented after clicking reload. Notice the version I'm running as of today's date stamp after I reloaded the C# extension. I hope this helps some of you. ! ! ! Be sure to click on the instance first, then use ctrl+. for windows ! You should now see the using statement, for example like on line 1 !

const hoverElement = $('div.hover-row.status-bar'); const disposables = new DisposableStore(); const actionsElement = dom.append(hoverElement, $('div.actions')); <del> disposables.add(this.renderAction(actionsElement, { label: nls.localize('quick fixes', "Quick Fix..."), commandId: QuickFixAction.Id, run: async (target) => { const codeActionsPromise = this.getCodeActions(markerHover.marker); disposables.add(toDisposable(() => codeActionsPromise.cancel())); const controller = QuickFixController.get(this._editor); const elementPosition = dom.getDomNodePagePosition(target); controller.showCodeActions(codeActionsPromise, { x: elementPosition.left + 6, y: elementPosition.top + elementPosition.height + 6 }); } })); </del> if (markerHover.marker.severity === MarkerSeverity.Error || markerHover.marker.severity === MarkerSeverity.Warning || markerHover.marker.severity === MarkerSeverity.Info) { disposables.add(this.renderAction(actionsElement, { label: nls.localize('peek problem', "Peek Problem"),


Question:
Hi, I am a bit new, and I have a simple code example on VS Code v1.32.3. It says I have an error, ok fine..... but then when I chose the "Quick Fix" option there is never a Quick Fix for this or any other thing in the past I tried to do a quick fix on. Whats the point of having a Quick Fix feature, if it doesn't do anything ? Im a bit confused. . This is the code I tried to do a quick fix on (its an extremely simple code): . ! When I try to fix, I get this: . !
I also get this issue for Python but seems to apply to any language. I have the Python extension as well as Intellicode. Still a current issue with 1.33 (Insiders) with the latest update.
Quick Fix... action is shown even when there are no quick fixes (code actions) available. May be it can hidden then.
Optimally, an actual corrective action would be taken (or at least suggested) based on the feedback provided by the language extensions (Python and Intellicode for my use-case).
Same here, I always get the "No code actions available" when I try to Quick Fix my code, no matter the language used, and even if I have no extension installed. ! ! I do not really know why it is not working, but I can't get to remember since when this bug is occurring to me ( I remember last summer it was okay, and I think during December too while I was working on an Angular Project )
Our C/C++ extensions does have lightbulb code actions for the error squiggle, but the quick fix still says "no code action" available -- is that a bug? Let us know if our extension isn't doing something correctly. I didn't understand the docs at . ! !
Can you please provide simple steps to repro this?
It occurs when you have a .c or .cpp file with text . We report the squiggle message via textDocumentpublishDiagnostics and the code action from textDocumentcodeAction. Do we need to do something special to associate the code action with the squiggle's QuickFix?
Quick Fix action asks for all code actions in that diagnostic range and of kind . What kind are your quick fix code actions?
Okay thanks a lot for informing us -- the "CodeActionKind" type is completely new to us. Our code action just returns a Command and not the additional info like the CodeActionKind. I filed a work item for us at . We have a lot of "catching up" to do with the LSP updates.
I have had this issue for weeks with C#, and I finally figured out that it was just the menu. Basic stuff where it used to suggest "using System;" no longer showed up. After reading this issue, I tried the command and the keyboard shortcut works but not the menu. This image shows what happens when clicking the "Quick fix..." menu: <img width="387" alt="screenshot from menu" src="https://user-"And this is what shows when pressing : <img width="414" alt="screenshot from keyboard" src="https://user-"This looks similar to the screenshots from and .
Seriously kills productivity, I am reinstalling PyCharm
Looks like C# extension is also not using the code action kind for their code actions. Probably we have to show all code actions for the given range.
I see the same issue with JSHint/JavaScript. ! !
The same thing (No code actions available) with PowerShell.
Same issue with TypeScript in .tsx file. ! !
This has been nearly two months! any fixes for this ? I'm having this issue in the latest version as well(Python)!
This feature becomes very important when you're upgrading code from a legacy version (such as Python 2) to the updated version (Python 3). I'm sure there are other languages have similar stipulations such as converting C to C++ or C# or vice versa (or even C# to C++ and vice versa).
I also have this issue, and this is very important when create the new project, but the works for me!
I also had this issue and only learned today from some searching that (on Linux) brings up the quick fix list of actual working suggestions EDIT: As shows below, that's the same issue I find when hovering using C#
This doesn't seem to be a problem for C# in my case atm (I'm using Unity/Mono). I exclusively use though.
I get the same with Powershell. ! ! However selecting it and press ctrl+. gave me the suggestion !
On a Mac, the Quick Fix shortcut appears to be ⌘. (Command + Period). It would be super helpful if we could get the quick fix to appear on mouse hover, though!
Hello there, I have the same problem since today. Quick fix was working a week ago but now clicking on "quick fix" and then clicking on suggestion do nothing. But if I use ctrl+; to show suggestion it work.
Just to clarify what was fixed by : we now only show the button in the hover if we know for sure that that quick fixes are available. A few extensions provide quick fix style code action but do not explicitly mark them as quick fixes. Those code actions will show up in the lightbulb menu but not if you click in errors hovers (because we only want to show code actions that we know for sure will fix something). Extensions must mark their quick fix code actions as  to have them show up in the problem hover menu too
can you verify that the python extension is good in this regard?
I took a look at my installed extensions and noticed the C# extension was complaining that it needed to be reloaded. Hmm, so check your extensions list first. This is what I was presented after clicking reload. Notice the version I'm running as of today's date stamp after I reloaded the C# extension. I hope this helps some of you. ! ! ! Be sure to click on the instance first, then use ctrl+. for windows ! You should now see the using statement, for example like on line 1 !

} })); } <ins> const quickfixPlaceholderElement = dom.append(actionsElement, $('div')); quickfixPlaceholderElement.style.opacity = '0'; quickfixPlaceholderElement.style.transition = 'opacity 0.2s'; setTimeout(() => quickfixPlaceholderElement.style.opacity = '1', 200); quickfixPlaceholderElement.textContent = nls.localize('checkingForQuickFixes', "Checking for quick fixes..."); disposables.add(toDisposable(() => quickfixPlaceholderElement.remove())); const codeActionsPromise = this.getCodeActions(markerHover.marker); disposables.add(toDisposable(() => codeActionsPromise.cancel())); codeActionsPromise.then(actions => { quickfixPlaceholderElement.style.transition = ''; quickfixPlaceholderElement.style.opacity = '1'; if (!actions.actions.length) { actions.dispose(); quickfixPlaceholderElement.textContent = nls.localize('noQuickFixes', "No quick fixes available"); return; } quickfixPlaceholderElement.remove(); let showing = false; disposables.add(toDisposable(() => { if (!showing) { actions.dispose(); } })); disposables.add(this.renderAction(actionsElement, { label: nls.localize('quick fixes', "Quick Fix..."), commandId: QuickFixAction.Id, run: (target) => { showing = true; const controller = QuickFixController.get(this._editor); const elementPosition = dom.getDomNodePagePosition(target); controller.showCodeActions(actions, { x: elementPosition.left + 6, y: elementPosition.top + elementPosition.height + 6 }); } })); }); </ins> this.renderDisposable.value = disposables; return hoverElement; } private getCodeActions(marker: IMarker): CancelablePromise<CodeActionSet> { <del> const noAction: CodeAction = { title: nls.localize('editor.action.quickFix.noneMessage', "No code actions available"), kind: CodeActionKind.QuickFix.value, }; return createCancelablePromise(async (cancellationToken): Promise<CodeActionSet> => { const result = await getCodeActions( </del> <ins> return createCancelablePromise(cancellationToken => { return getCodeActions( </ins> this._editor.getModel()!, new Range(marker.startLineNumber, marker.startColumn, marker.endLineNumber, marker.endColumn), { type: 'manual', filter: { kind: CodeActionKind.QuickFix } }, cancellationToken); <del> return { actions: result.actions.length ? result.actions : [noAction], hasAutoFix: result.hasAutoFix, dispose: () => result.dispose(), }; </del> }); }


Question:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Seems to work just fine for me... Any special keybinding or setting? !
The action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit "SystemName", the first tab stop, then press TAB to go to "Required Components"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.
Ok, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why
I have encountered similar issue, however, I could add a single blank space in the snippet which "fixed" the tab navigation. Also, my example is far simpler. See
This is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)
Thank you for fixing this, looking forward to the next release.

import { KeybindingWeight } from 'vs/platform/keybinding/common/keybindingsRegistry'; import { ILogService } from 'vs/platform/log/common/log'; import { SnippetSession } from './snippetSession'; <del> import { EditorState, CodeEditorStateFlag } from 'vs/editor/browser/core/editorState'; </del> export class SnippetController2 implements IEditorContribution {


Question:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Seems to work just fine for me... Any special keybinding or setting? !
The action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit "SystemName", the first tab stop, then press TAB to go to "Required Components"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.
Ok, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why
I have encountered similar issue, however, I could add a single blank space in the snippet which "fixed" the tab navigation. Also, my example is far simpler. See
This is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)
Thank you for fixing this, looking forward to the next release.

this._updateState(); <del> // we listen on model and selection changes. usually // both events come in together and this is to prevent // that we don't call _updateState twice. let state: EditorState; let dedupedUpdateState = () => { if (!state || !state.validate(this._editor)) { this._updateState(); state = new EditorState(this._editor, CodeEditorStateFlag.Selection | CodeEditorStateFlag.Value); } }; </del> this._snippetListener = [ <del> this._editor.onDidChangeModelContent(e => { if (e.isFlush) { this.cancel(); } else { setTimeout(dedupedUpdateState, 0); } }), this._editor.onDidChangeCursorSelection(dedupedUpdateState), </del> <ins> this._editor.onDidChangeModelContent(e => e.isFlush && this.cancel()), </ins> this._editor.onDidChangeModel(() => this.cancel()), <ins> this._editor.onDidChangeCursorSelection(() => this._updateState()) </ins> ]; }


Question:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Seems to work just fine for me... Any special keybinding or setting? !
The action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit "SystemName", the first tab stop, then press TAB to go to "Required Components"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.
Ok, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why
I have encountered similar issue, however, I could add a single blank space in the snippet which "fixed" the tab navigation. Also, my example is far simpler. See
This is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)
Thank you for fixing this, looking forward to the next release.

let ranges: Range[] | undefined; for (const placeholder of placeholdersWithEqualIndex) { <ins> if (placeholder.isFinalTabstop) { // ignore those break; } </ins> if (!ranges) { ranges = [];


Question:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Seems to work just fine for me... Any special keybinding or setting? !
The action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit "SystemName", the first tab stop, then press TAB to go to "Required Components"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.
Ok, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why
I have encountered similar issue, however, I could add a single blank space in the snippet which "fixed" the tab navigation. Also, my example is far simpler. See
This is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)
Thank you for fixing this, looking forward to the next release.

return false; } <del> if (allPossibleSelections.has(0)) { // selection overlaps with a final tab stop which means // we done return false; } </del> // add selections from 'this' snippet so that we know all // selections for this placeholder allPossibleSelections.forEach((array, index) => {


Question:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Seems to work just fine for me... Any special keybinding or setting? !
The action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit "SystemName", the first tab stop, then press TAB to go to "Required Components"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.
Ok, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why
I have encountered similar issue, however, I could add a single blank space in the snippet which "fixed" the tab navigation. Also, my example is far simpler. See
This is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)
Thank you for fixing this, looking forward to the next release.

import { ICodeEditor } from 'vs/editor/browser/editorBrowser'; import { NullLogService } from 'vs/platform/log/common/log'; import { Handler } from 'vs/editor/common/editorCommon'; <del> import { timeout } from 'vs/base/common/async'; </del> suite('SnippetController2', function () {


Question:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Seems to work just fine for me... Any special keybinding or setting? !
The action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit "SystemName", the first tab stop, then press TAB to go to "Required Components"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.
Ok, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why
I have encountered similar issue, however, I could add a single blank space in the snippet which "fixed" the tab navigation. Also, my example is far simpler. See
This is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)
Thank you for fixing this, looking forward to the next release.

assertSelections(editor, new Selection(1, 1, 1, 7), new Selection(2, 5, 2, 11)); editor.trigger('test', 'cut', {}); <del> assertContextKeys(contextKeys, false, false, false); </del> <ins> assertContextKeys(contextKeys, true, false, true); </ins> assertSelections(editor, new Selection(1, 1, 1, 1), new Selection(2, 5, 2, 5)); editor.trigger('test', 'type', { text: 'abc' }); <del> assertContextKeys(contextKeys, false, false, false); </del> <ins> assertContextKeys(contextKeys, true, false, true); </ins> ctrl.next(); assertContextKeys(contextKeys, false, false, false);


Question:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Seems to work just fine for me... Any special keybinding or setting? !
The action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit "SystemName", the first tab stop, then press TAB to go to "Required Components"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.
Ok, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why
I have encountered similar issue, however, I could add a single blank space in the snippet which "fixed" the tab navigation. Also, my example is far simpler. See
This is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)
Thank you for fixing this, looking forward to the next release.

assertSelections(editor, new Selection(1, 4, 1, 4), new Selection(2, 8, 2, 8)); assertContextKeys(contextKeys, true, false, true); <del> // ctrl.next(); // assertSelections(editor, new Selection(1, 7, 1, 7), new Selection(2, 11, 2, 11)); // assertContextKeys(contextKeys, true, true, true); </del> <ins> ctrl.next(); assertSelections(editor, new Selection(1, 7, 1, 7), new Selection(2, 11, 2, 11)); assertContextKeys(contextKeys, true, true, true); </ins> ctrl.next(); assertSelections(editor, new Selection(1, 7, 1, 7), new Selection(2, 11, 2, 11));


Question:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Seems to work just fine for me... Any special keybinding or setting? !
The action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit "SystemName", the first tab stop, then press TAB to go to "Required Components"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.
Ok, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why
I have encountered similar issue, however, I could add a single blank space in the snippet which "fixed" the tab navigation. Also, my example is far simpler. See
This is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)
Thank you for fixing this, looking forward to the next release.

ctrl.insert('farboo'); assertSelections(editor, new Selection(1, 7, 1, 7), new Selection(2, 11, 2, 11)); <del> // assertContextKeys(contextKeys, true, false, true); </del> <ins> assertContextKeys(contextKeys, true, false, true); </ins> <del> // ctrl.next(); // assertSelections(editor, new Selection(1, 7, 1, 7), new Selection(2, 11, 2, 11)); </del> <ins> ctrl.next(); assertSelections(editor, new Selection(1, 7, 1, 7), new Selection(2, 11, 2, 11)); </ins> assertContextKeys(contextKeys, false, false, false); });


Question:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Seems to work just fine for me... Any special keybinding or setting? !
The action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit "SystemName", the first tab stop, then press TAB to go to "Required Components"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.
Ok, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why
I have encountered similar issue, however, I could add a single blank space in the snippet which "fixed" the tab navigation. Also, my example is far simpler. See
This is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)
Thank you for fixing this, looking forward to the next release.

assertSelections(editor, new Selection(1, 22, 1, 22)); }); <del> test('A little confusing visual effect of highlighting for snippet tabstop #43270', async function () { </del> <ins> test('User defined snippet tab stops ignored #72862', function () { </ins> const ctrl = new SnippetController2(editor, logService, contextKeys); model.setValue(''); editor.setSelection(new Selection(1, 1, 1, 1)); <del> ctrl.insert('background-color: ${1:fff};$0'); assertSelections(editor, new Selection(1, 19, 1, 22)); editor.setSelection(new Selection(1, 22, 1, 22)); </del> <ins> ctrl.insert('export default $1'); </ins> assertContextKeys(contextKeys, true, false, true); <del> editor.trigger('', 'deleteRight', null); assert.equal(model.getValue(), 'background-color: fff'); await timeout(0); // this depends on re-scheduling of events... assertContextKeys(contextKeys, false, false, false); </del> }); });


Question:
<!-- Please search existing issues to avoid creating duplicates. --<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: --<!-- Use Help Report Issue to prefill these. --- VSCode Version: 1.33.1 OS Version: Windows_NT x64 10.0. Steps to Reproduce: a new user snippet file for the project. The one I encounter the issue with is: the snippet and attempt to press TAB after writing the first variable cursor does not move to the next stop, instead a tab character is The desired behavior would be for the cursor to move to the next tab stop. <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes
Seems to work just fine for me... Any special keybinding or setting? !
The action you took is not the problem I encounter and does indeed work the same way for me. Could you try to edit "SystemName", the first tab stop, then press TAB to go to "Required Components"? vsCode just inserts a tab character after whatever I wrote instead of going to the next tab stop.
Ok, thanks for clarifying. For some reason snippet mode stops when making that edit... Not sure why
I have encountered similar issue, however, I could add a single blank space in the snippet which "fixed" the tab navigation. Also, my example is far simpler. See
This is a regression from I will revert that change and re-open the corresponding issue (which is much more rare than these issues)
Thank you for fixing this, looking forward to the next release.

// reset selection to placeholder session.next(); <del> assert.equal(session.isSelectionWithinPlaceholders(), false); </del> <ins> assert.equal(session.isSelectionWithinPlaceholders(), true); </ins> assert.equal(session.isAtLastPlaceholder, true); assertSelections(editor, new Selection(1, 13, 1, 13), new Selection(2, 17, 2, 17)); });


Question:
VSCode Version: 1.33.1 OS Version: WindowsNT x64 10.0. Steps to Reproduce: folder (Ctrl+K F) a search on specified path through Ctrl+Shift+F ! With literally any folder on my system opened search works: ! I'm not sure if this is intended behavior, as the message suggests that it shouldn't work if I don't have that particular_ folder currently opened anyways, and yet it does if I open anything. Does this issue occur when all extensions are disabled?: Yes
I was just about to file an issue to find out if searching an arbitrary folder / folder tree was even possible since the note says only the currently opened folder will be searched. This is one of the things Sublime has that I was hoping VS Code had. I never tried opening any ol' folder and giving it a run.
, can i take a look at this ?
Should fix the message 'You have not yet opened a folder. Only open files are currently searched - Open Folder' makes it sound like my searches will fail with no folder open, but as long as I plug a path in it works like the issue specifies. Maybe add something along the lines of 'unless a path is specified'
I could say, "You have not opened or specified a folder, ..." I'm not sure if that's too wordy, I don't think a warning message has to explain how the whole thing works, what do you think?
Make sure you reopen issues when they are "verification-found"
This would work. How would it work once I specified a folder but haven't hit send would the message go away due to having a valid path?
No, I think it should just be updated once when the search actually runs
That seems like it would work, it would at least imply that the action being performed would work.
Now it makes more sense !

* Split search paths (./ or ../ or absolute paths in the includePatterns) into absolute paths and globs applied to those paths */ private expandSearchPathPatterns(searchPaths: string[]): ISearchPathPattern[] { <del> if (this.workspaceContextService.getWorkbenchState() === WorkbenchState.EMPTY || !searchPaths || !searchPaths.length) { </del> <ins> if (!searchPaths || !searchPaths.length) { </ins> // No workspace => ignore search paths return []; }


Question:
Issue Type: <bBug</bHi. I am assigning trade.occId = occId; i.e. to a property (in this case it contains 4 spaces. In the JavaScript hover view however, the property on 'trade' reads (only one space) [btw, I copied both these values right out of the IDE view]. I've just been chasing ghosts for some time because of this discrepancy and not expecting the IDE altering assigned values when viewing objects. Update ---Alright, sorry. I am not sure how to submit the first value on GitHub with the 4 spaces between GS and 1 preserved, even when using 'code' quotes (same as the VSC issue...). So the first value is "GD....190517P00155000" when replacing spaces with dots... Thanks for VS Code otherwise :-) VS Code version: Code 1.33.1 (, 2019-04-11T08:27:14.102Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (4)</summaryExtensionVersion ------ vscode-scss0.6.2 debugger-for-chrome4.11.3 vscode-scss-formatter1.4.1 vscodeintellicode1.1.5 </details<!-- generated by issue reporter --
Can you please provide a screenshot of what you see? Also try disabling all extensions. I am not sure if such an hover is provided by out of the box typescript/javascript extension.
Hi. Please see below. I disabled all extensions besides Debugger for Chrome, which I need to set a break-point to be able to inspect values. The issue is in most obvious in the field 'occId', which in fact has 4 spaces after 'GD' and not just one as displayed. Thanks for following up. [image: ] !
Ah I see.. its an hover while debugging.
You did not attach an image. So please attach an image and some reproducable steps so we can investigate more. Thanks
It did, (please check below the quote). Anyway, your question made me come up with a better/simpler example that should make things clear. Here you go: ! Btw, Gruetzi to all you guys in Zuerich. I'm originally from Basel :)
Thanks for the image. Cheers back to Basel :)
VSCode insiders will have the fix for this on monday. Try it out and let us know if it is ok for you. Though I verified and the fix from looks good
Thanks for the work and update. Unfortunately I can't switch from VSCode stable, so I'll take your word for it until this hits release :-)

import { IInstantiationService } from 'vs/platform/instantiation/common/instantiation'; import { IDebugService, IExpression, IExpressionContainer } from 'vs/workbench/contrib/debug/common/debug'; import { Expression } from 'vs/workbench/contrib/debug/common/debugModel'; <del> import { renderExpressionValue } from 'vs/workbench/contrib/debug/browser/baseDebugView'; </del> <ins> import { renderExpressionValue, replaceWhitespace } from 'vs/workbench/contrib/debug/browser/baseDebugView'; </ins> import { DomScrollableElement } from 'vs/base/browser/ui/scrollbar/scrollableElement'; import { attachStylerCallback } from 'vs/platform/theme/common/styler'; import { IThemeService } from 'vs/platform/theme/common/themeService';


Question:
Issue Type: <bBug</bHi. I am assigning trade.occId = occId; i.e. to a property (in this case it contains 4 spaces. In the JavaScript hover view however, the property on 'trade' reads (only one space) [btw, I copied both these values right out of the IDE view]. I've just been chasing ghosts for some time because of this discrepancy and not expecting the IDE altering assigned values when viewing objects. Update ---Alright, sorry. I am not sure how to submit the first value on GitHub with the 4 spaces between GS and 1 preserved, even when using 'code' quotes (same as the VSC issue...). So the first value is "GD....190517P00155000" when replacing spaces with dots... Thanks for VS Code otherwise :-) VS Code version: Code 1.33.1 (, 2019-04-11T08:27:14.102Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (4)</summaryExtensionVersion ------ vscode-scss0.6.2 debugger-for-chrome4.11.3 vscode-scss-formatter1.4.1 vscodeintellicode1.1.5 </details<!-- generated by issue reporter --
Can you please provide a screenshot of what you see? Also try disabling all extensions. I am not sure if such an hover is provided by out of the box typescript/javascript extension.
Hi. Please see below. I disabled all extensions besides Debugger for Chrome, which I need to set a break-point to be able to inspect values. The issue is in most obvious in the field 'occId', which in fact has 4 spaces after 'GD' and not just one as displayed. Thanks for following up. [image: ] !
Ah I see.. its an hover while debugging.
You did not attach an image. So please attach an image and some reproducable steps so we can investigate more. Thanks
It did, (please check below the quote). Anyway, your question made me come up with a better/simpler example that should make things clear. Here you go: ! Btw, Gruetzi to all you guys in Zuerich. I'm originally from Basel :)
Thanks for the image. Cheers back to Basel :)
VSCode insiders will have the fix for this on monday. Try it out and let us know if it is ok for you. Though I verified and the fix from looks good
Thanks for the work and update. Unfortunately I can't switch from VSCode stable, so I'll take your word for it until this hits release :-)

this.complexValueContainer.hidden = false; return this.tree.setInput(expression).then(() => { <del> this.complexValueTitle.textContent = expression.value; </del> <ins> this.complexValueTitle.textContent = replaceWhitespace(expression.value); </ins> this.complexValueTitle.title = expression.value; this.layoutTreeAndContainer(); this.editor.layoutContentWidget(this);


Question:
Issue Type: <bBug</bHi. I am assigning trade.occId = occId; i.e. to a property (in this case it contains 4 spaces. In the JavaScript hover view however, the property on 'trade' reads (only one space) [btw, I copied both these values right out of the IDE view]. I've just been chasing ghosts for some time because of this discrepancy and not expecting the IDE altering assigned values when viewing objects. Update ---Alright, sorry. I am not sure how to submit the first value on GitHub with the 4 spaces between GS and 1 preserved, even when using 'code' quotes (same as the VSC issue...). So the first value is "GD....190517P00155000" when replacing spaces with dots... Thanks for VS Code otherwise :-) VS Code version: Code 1.33.1 (, 2019-04-11T08:27:14.102Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (4)</summaryExtensionVersion ------ vscode-scss0.6.2 debugger-for-chrome4.11.3 vscode-scss-formatter1.4.1 vscodeintellicode1.1.5 </details<!-- generated by issue reporter --
Can you please provide a screenshot of what you see? Also try disabling all extensions. I am not sure if such an hover is provided by out of the box typescript/javascript extension.
Hi. Please see below. I disabled all extensions besides Debugger for Chrome, which I need to set a break-point to be able to inspect values. The issue is in most obvious in the field 'occId', which in fact has 4 spaces after 'GD' and not just one as displayed. Thanks for following up. [image: ] !
Ah I see.. its an hover while debugging.
You did not attach an image. So please attach an image and some reproducable steps so we can investigate more. Thanks
It did, (please check below the quote). Anyway, your question made me come up with a better/simpler example that should make things clear. Here you go: ! Btw, Gruetzi to all you guys in Zuerich. I'm originally from Basel :)
Thanks for the image. Cheers back to Basel :)
VSCode insiders will have the fix for this on monday. Try it out and let us know if it is ok for you. Though I verified and the fix from looks good
Thanks for the work and update. Unfortunately I can't switch from VSCode stable, so I'll take your word for it until this hits release :-)

overflow: hidden; text-overflow: ellipsis; font-family: var(--monaco-monospace-font); <ins> white-space: pre; </ins> } .monaco-workbench.mac .debug-viewlet .monaco-list-row .expression,


Question:
Issue Type: <bBug</bHi. I am assigning trade.occId = occId; i.e. to a property (in this case it contains 4 spaces. In the JavaScript hover view however, the property on 'trade' reads (only one space) [btw, I copied both these values right out of the IDE view]. I've just been chasing ghosts for some time because of this discrepancy and not expecting the IDE altering assigned values when viewing objects. Update ---Alright, sorry. I am not sure how to submit the first value on GitHub with the 4 spaces between GS and 1 preserved, even when using 'code' quotes (same as the VSC issue...). So the first value is "GD....190517P00155000" when replacing spaces with dots... Thanks for VS Code otherwise :-) VS Code version: Code 1.33.1 (, 2019-04-11T08:27:14.102Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (4)</summaryExtensionVersion ------ vscode-scss0.6.2 debugger-for-chrome4.11.3 vscode-scss-formatter1.4.1 vscodeintellicode1.1.5 </details<!-- generated by issue reporter --
Can you please provide a screenshot of what you see? Also try disabling all extensions. I am not sure if such an hover is provided by out of the box typescript/javascript extension.
Hi. Please see below. I disabled all extensions besides Debugger for Chrome, which I need to set a break-point to be able to inspect values. The issue is in most obvious in the field 'occId', which in fact has 4 spaces after 'GD' and not just one as displayed. Thanks for following up. [image: ] !
Ah I see.. its an hover while debugging.
You did not attach an image. So please attach an image and some reproducable steps so we can investigate more. Thanks
It did, (please check below the quote). Anyway, your question made me come up with a better/simpler example that should make things clear. Here you go: ! Btw, Gruetzi to all you guys in Zuerich. I'm originally from Basel :)
Thanks for the image. Cheers back to Basel :)
VSCode insiders will have the fix for this on monday. Try it out and let us know if it is ok for you. Though I verified and the fix from looks good
Thanks for the work and update. Unfortunately I can't switch from VSCode stable, so I'll take your word for it until this hits release :-)

text-overflow: ellipsis; height: 18px; overflow: hidden; <ins> white-space: pre; </ins> border-bottom: 1px solid rgba(128, 128, 128, 0.35); }