text:
HTML Intellisense NOT working as expected.

Issue Type: Bug
My intellisense isn't working like before for HTML. I checked my settings and the checkbox for the HTML extensions is checked (enabled).
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-11T01:11:34.018Z)
OS version: Darwin x64 20.1.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6287U CPU @ 3.10GHz (4 x 3100)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 3

Memory (System)
16.00GB (6.36GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.1.13

prettier-vscode
esb
5.8.0

beautify
Hoo
1.5.0

jupyter
ms-
2020.11.399280825

Is it this issue: https://github.com/microsoft/vscode/issues/110971

Is it this issue: #110971 You don't really explain what you see: nothing, just one line, or how it isn't working.
If you are just seeing one line of intellisense info, just drag the lower border down to increase its height.

No. In my case, if I start out typing "<div" it suggests "" but does NOT provide the closing tag "".

But as soon as you type >, the tag will be closed?

No. I'm forced to type the entire opening AND closing tags.

You said it worked before right?

make sure that the editor mode is HTML (status bar lower right)

make sure the html language feature extension is enabled

I've confirmed the language extension is enabled. I'm using HTML inside a ReactJS components render. Pl

ease see the attached.

We don't have the auto close feature in JavaScript/TypeScript files.

@evboggs302  Please share a complete code example that demonstrates the problem

We don't have the auto close feature in JavaScript/TypeScript files.

It was previously working. Not sure when it stopped, but i know for a fact it was working in the same situation in which I've described to you.

@vboggs302 what situation? Please share a complete code example along with steps to reproduce the problem, and then precisely describe the expected behavior

In summary thus far:

My intellisense isn't working like before for HTML.
I checked my settings and the checkbox for the HTML extensions is checked (enabled).
I've confirmed the language extension is enabled.
I'm using HTML inside a ReactJS components render.

Code Example: Any js file in this directory https://github.com/evboggs302/productplan-candidate-homework/tree/master/productplan-homework/src/Components
The expected behavior: When typing any HTML element in a JS file (React), intellisense used to and should be able to auto complete the HTML element I'm creating. See photos above as examples of it NOT doing that.

Please share a minimal example @evboggs302. It's not a good use for time for maintainers to try debugging through your complete project

https://github.com/evboggs302/productplan-candidate-homework/blob/master/productplan-homework/src/App.js

What am I supposed to do in that file to reproduce this?

authors: ArturoDent aeschli evboggs302 mjbvz


text:
Change workbench.editor.enablePreview default to false

Creating issue for discussion based on #115088
For background, see https://stackoverflow.com/questions/38713405/open-files-always-in-a-new-tab
Current: workbench.editor.enablePreview default true. Newly opened files open over the current file being edited
Expected/sane: workbench.editor.enablePreview default false.
There are numerous requests in this stackoverflow post to change the default behaviour to more sane default of new file opens being done in a new tab instead of over the existing tab.
This would follow the principle of least astonishment and be more similar to how browsers open (_blank) links in new tab.
I have to change this setting every time on a new instance.
I have not heard a case where someone prefers the current default behaviour to the more expected conventional one.
I can reopen #115088 if it is decided this is the way to go.
Thanks,

I personally prefer the current default behavior. Especially when navigating through projects with many files, I often end up having too many files open and lose track. The current behavior helps to tackle that problem, it keeps VS Code cleaner by default.
It is also not hard to go back when that happens, using the menu (Go > Back) or ctrl+alt+-. And, as mentioned on StackOverflow too, this can be easily avoided by double-clicking the file.
I understand that this behavior is a bit surprising at first though and might need some time to get used to. What I would suggest instead is that the preview editors should be visually more different from the normal editors - the italic font in the tab title can easily be overlooked. I'm not a UI designer, but something like a different background shade in the editor or some kind of border around it would work.

I personally prefer the current default behavior. Especially when navigating through projects with many files, I often end up having too many files open and lose track. The current behavior helps to tackle that problem, it keeps VS Code cleaner by default.
It is also not hard to go back when that happens, using the menu (Go > Back) or ctrl+alt+-. And, as mentioned on StackOverflow too, this can be easily avoided by double-clicking the file.
I understand that this behavior is a bit surprising at first though and might need some time to get used to. What I would suggest instead is that the preview editors should be visually more different from the normal editors - the italic font in the tab title can easily be overlooked. I'm not a UI designer, but something like a different background shade in the editor or some kind of border around it would work.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

if my original post has 20 upvotes ?

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

if my original post has 20 upvotes ?

source: gharchive/issue

authors: goldst wesinator

repo: microsoft/vscode

license: MIT

license_type: permissive

license_source: github-api


text:
Startup performance issue window_load

System Info

Code: 1.55.2 (3c4e3df9e89829dce27b7b5c24508306b151f30d)
OS: win32(10.0.21354)
CPUs: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz(12 x 3300)
Memory(System): 31.90 GB(26.09GB free)
Memory(Process): 192.58 MB working set(166.02MB private, 1.16MB shared)
VM(likelihood): 80%
Initial Startup: true
Has 0 other windows
Screen Reader Active: false
Empty Workspace: true

Performance Marks

What
Duration
Process
Info

start => app.isReady
83
[main]
initial startup: true

nls:start => nls:end
0
[main]
initial startup: true

require(main.bundle.js)
125
[main]
initial startup: true

app.isReady => window.loadUrl()
368
[main]
initial startup: true

window.loadUrl() => begin to require(workbench.desktop.main.js)
7099
[main->renderer]
NewWindow

require(workbench.desktop.main.js)
849
[renderer]
cached data: NO, node_modules took 0ms

wait for shell environment
0
[renderer]
-

init storage (global & workspace)
53
[renderer]
-

init workspace service
44
[renderer]
-

register extensions & spawn extension host
352
[renderer]
-

restore viewlet
0
[renderer]
-

restore panel
0
[renderer]
-

restore editors
128
[renderer]
1: PerfviewInput

overall workbench load
486
[renderer]
-

workbench ready
8950
[main->renderer]
-

renderer ready
1406
[renderer]
-

shared process connection ready
0
[renderer->sharedprocess]
-

extensions registered
9389
[renderer]
-

Extension Activation Stats

Extension
Eager
Load Code
Call Activate
Finish Activate
Event
By

vscode.debug-auto-launch
true
5
0
41
*
vscode.debug-auto-launch

vscode.git
true
87
7
63
*
vscode.github

vscode.github
true
9
0
0
*
vscode.github

christian-kohler.path-intellisense
true
41
0
34
*
christian-kohler.path-intellisense

CoenraadS.bracket-pair-colorizer-2
true
42
24
10
*
CoenraadS.bracket-pair-colorizer-2

donjayamanne.githistory
true
80
10
0
*
donjayamanne.githistory

EditorConfig.EditorConfig
true
40
0
0
*
EditorConfig.EditorConfig

vscode.emmet
false
24
2
4
onStartupFinished
vscode.emmet

vscode.extension-editing
false
29
0
44
onLanguage:markdown
vscode.extension-editing

vscode.github-authentication
false
23
2
151
onAuthenticationRequest:github
vscode.github-authentication

vscode.markdown-language-features
false
78
3
41
onLanguage:markdown
vscode.markdown-language-features

vscode.merge-conflict
false
4
1
3
onStartupFinished
vscode.merge-conflict

vscode.microsoft-authentication
false
38
4
848
onAuthenticationRequest:microsoft
vscode.microsoft-authentication

ms-vscode-remote.remote-wsl-recommender
false
19
2
2
onStartupFinished
ms-vscode-remote.remote-wsl-recommender

ms-vscode.js-debug
false
203
7
0
onCommand:extension.js-debug.clearAutoAttachVariables
ms-vscode.js-debug

vscode.testing-editor-contributions
false
1
0
2
onStartupFinished
vscode.testing-editor-contributions

eamodio.gitlens
false
118
1
63
onStartupFinished
eamodio.gitlens

ms-vscode-remote.remote-containers
false
85
0
637
onStartupFinished
ms-vscode-remote.remote-containers

ryu1kn.partial-diff
false
98
0
7
onStartupFinished
ryu1kn.partial-diff

Raw Perf Marks: main
Name	Timestamp	Delta	Total
code/timeOrigin	1618430351997	0	0
code/didStartMain	1618430352637	640	640
code/mainAppReady	1618430352720	83	723
code/willLoadMainBundle	1618430352720	0	723
code/fork/willLoadCode	1618430352739	19	742
code/registerFilesystem/file	1618430352841	102	844
code/didLoadMainBundle	1618430352845	4	848
code/willOpenNewWindow	1618430353088	243	1091

Raw Perf Marks: renderer
Name	Timestamp	Delta	Total
code/timeOrigin	1618430353086	0	0
code/didStartRenderer	1618430360181	7095	7095
code/willShowPartsSplash	1618430360182	1	7096
code/didShowPartsSplash	1618430360183	1	7097
code/willLoadWorkbenchMain	1618430360187	4	7101
code/willWaitForShellEnv	1618430361035	848	7949
code/didWaitForShellEnv	1618430361035	0	7949
code/didLoadWorkbenchMain	1618430361036	1	7950
code/registerFilesystem/file	1618430361041	5	7955
code/registerFilesystem/vscode-userdata	1618430361041	0	7955
code/willInitWorkspaceService	1618430361046	5	7960
code/willInitStorage	1618430361047	1	7961
code/didInitWorkspaceService	1618430361090	43	8004
code/didInitStorage	1618430361100	10	8014
code/willStartWorkbench	1618430361101	1	8015
code/LifecyclePhase/Ready	1618430361105	4	8019
code/registerFilesystem/trustedDomains	1618430361230	125	8144
code/willRestoreEditors	1618430361459	229	8373
code/didRestoreEditors	1618430361587	128	8501
code/LifecyclePhase/Restored	1618430361587	0	8501
code/didStartWorkbench	1618430361587	0	8501
code/didRemovePartsSplash	1618430361587	0	8501
code/willConnectSharedProcess	1618430361607	20	8521
code/willLoadExtensions	1618430361674	67	8588
code/willHandleExtensionPoints	1618430361828	154	8742
code/didHandleExtensionPoints	1618430362020	192	8934
code/didLoadExtensions	1618430362026	6	8940

Raw Perf Marks: localExtHost
Name	Timestamp	Delta	Total
code/timeOrigin	1618430363770	0	0
code/fork/start	1618430363985	215	215
code/fork/willLoadCode	1618430364016	31	246
code/extHost/willConnectToRenderer	1618430364351	335	581
code/extHost/didConnectToRenderer	1618430364352	1	582
code/extHost/didWaitForInitData	1618430364423	71	653
code/extHost/didCreateServices	1618430364435	12	665
code/extHost/willWaitForConfig	1618430364439	4	669
code/extHost/didWaitForConfig	1618430364486	47	716
code/extHost/didInitAPI	1618430364491	5	721
code/extHost/didInitProxyResolver	1618430364492	1	722
code/extHost/ready	1618430364492	0	722
code/extHost/willLoadExtensionCode/vscode.microsoft-authentication	1618430364520	28	750
code/extHost/didLoadExtensionCode/vscode.microsoft-authentication	1618430364558	38	788
code/extHost/willLoadExtensionCode/vscode.extension-editing	1618430364558	0	788
code/extHost/didLoadExtensionCode/vscode.extension-editing	1618430364587	29	817
code/extHost/willLoadExtensionCode/vscode.markdown-language-features	1618430364588	1	818
code/extHost/didLoadExtensionCode/vscode.markdown-language-features	1618430364666	78	896
code/extHost/willLoadExtensionCode/vscode.debug-auto-launch	1618430364666	0	896
code/extHost/didLoadExtensionCode/vscode.debug-auto-launch	1618430364671	5	901
code/extHost/willLoadExtensionCode/vscode.git	1618430364671	0	901
code/extHost/didLoadExtensionCode/vscode.git	1618430364758	87	988
code/extHost/willLoadExtensionCode/christian-kohler.path-intellisense	1618430364759	1	989
code/extHost/didLoadExtensionCode/christian-kohler.path-intellisense	1618430364800	41	1030
code/extHost/willLoadExtensionCode/CoenraadS.bracket-pair-colorizer-2	1618430364800	0	1030
code/extHost/didLoadExtensionCode/CoenraadS.bracket-pair-colorizer-2	1618430364842	42	1072
code/extHost/willLoadExtensionCode/donjayamanne.githistory	1618430364843	1	1073
code/extHost/didLoadExtensionCode/donjayamanne.githistory	1618430364923	80	1153
code/extHost/willLoadExtensionCode/EditorConfig.EditorConfig	1618430364923	0	1153
code/extHost/didLoadExtensionCode/EditorConfig.EditorConfig	1618430364963	40	1193
code/extHost/willActivateExtension/vscode.microsoft-authentication	1618430364971	8	1201
code/extHost/willActivateExtension/vscode.extension-editing	1618430364975	4	1205
code/extHost/willActivateExtension/vscode.markdown-language-features	1618430364975	0	1205
code/extHost/willActivateExtension/vscode.debug-auto-launch	1618430364978	3	1208
code/extHost/willActivateExtension/vscode.git	1618430364978	0	1208
code/extHost/willActivateExtension/christian-kohler.path-intellisense	1618430364985	7	1215
code/extHost/willActivateExtension/CoenraadS.bracket-pair-colorizer-2	1618430364985	0	1215
code/extHost/willActivateExtension/donjayamanne.githistory	1618430365009	24	1239
code/extHost/willActivateExtension/EditorConfig.EditorConfig	1618430365019	10	1249
code/extHost/didActivateExtension/vscode.extension-editing	1618430365019	0	1249
code/extHost/didActivateExtension/vscode.markdown-language-features	1618430365019	0	1249
code/extHost/didActivateExtension/vscode.debug-auto-launch	1618430365019	0	1249
code/extHost/didActivateExtension/christian-kohler.path-intellisense	1618430365019	0	1249
code/extHost/didActivateExtension/CoenraadS.bracket-pair-colorizer-2	1618430365019	0	1249
code/extHost/didActivateExtension/donjayamanne.githistory	1618430365019	0	1249
code/extHost/didActivateExtension/EditorConfig.EditorConfig	1618430365019	0	1249
code/extHost/didActivateExtension/vscode.git	1618430365048	29	1278
code/extHost/willLoadExtensionCode/vscode.github	1618430365802	754	2032
code/extHost/didLoadExtensionCode/vscode.github	1618430365811	9	2041
code/extHost/didActivateExtension/vscode.microsoft-authentication	1618430365825	14	2055
code/extHost/willActivateExtension/vscode.github	1618430365842	17	2072
code/extHost/didActivateExtension/vscode.github	1618430365842	0	2072

Node Cached Data Stats
cached data used
cached data missed
cached data rejected
cached data created (lazy, might need refreshes)
prof-bad1.renderer.cpuprofile.txt
prof-bad1.extHost.cpuprofile.txt
prof-bad1.main.cpuprofile.txt

Why does VsCode do so many things at startup serialized ?

It seems to be some regression here https://github.com/microsoft/vscode/blob/c8af1d0c550b6e6a06e01d08bddc978949f65927/src/vs/code/electron-main/windows.ts#L1275

having the same issue lately. startup performance slowed over the last two releases or so

Based on https://github.com/microsoft/vscode/issues/121377#issuecomment-838976898 the issue seems to be fixed with windows build 21376, @Luiz-Monad can you update and check. Thanks!

Working !

authors: Luiz-Monad alexanderniebuhr deepak1556


text:
command "code-insider ." do not work properly

Issue Type: Bug
command code-insider . do not work properly. This command must to open project in current folder but instead it open empty project
Steps to reproduce:

In wsl go to project folder
cd /project/folder
then type
code-insiders .

Expected result
Open project in this folder
Actual result
VSCode opened empty project or last opened project from other dir
Also reproduced with disabled extensions
VS Code version: Code - Insiders 1.63.0-insider (ed3018f4310e906daa0a9119d997e75b8a38b879, 2021-11-23T05:33:39.595Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
Remote OS version: Linux x64 5.10.60.1-microsoft-standard-WSL2

System Info

Item
Value

CPUs
AMD Ryzen 5 5600X 6-Core Processor              (12 x 3700)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.92GB (5.48GB free)

Process Argv
--remote=wsl+Ubuntu-20.04 --crash-reporter-id cac02e12-1b29-4401-90b4-691c0715a32a

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu-20.04

OS
Linux x64 5.10.60.1-microsoft-standard-WSL2

CPUs
AMD Ryzen 5 5600X 6-Core Processor (12 x 3700)

Memory (System)
7.72GB (4.30GB free)

VM
0%

Extensions (41)

Extension
Author (truncated)
Version

vsc-material-theme
Equ
33.2.0

vsc-material-theme-icons
equ
1.2.2

dotenv
mik
1.0.1

vscode-apache
mrm
1.2.0

vscode-edge-devtools
ms-
1.4.1

remote-containers
ms-
0.206.0

remote-wsl
ms-
0.63.2

laravel5-snippets
one
1.13.0

material-icon-theme
PKi
4.10.0

code-settings-sync
Sha
3.4.3

errorlens
use
3.4.1

vscode-openapi
42C
4.6.4

vscode-sqlite
ale
0.14.0

vscode-intelephense-client
bme
1.7.1

vscode-tailwindcss
bra
0.7.2

better-phpunit
cal
1.5.3

vscode-eslint
dba
2.2.2

xml
Dot
2.5.1

gitlens
eam
11.7.0

vscode-npm-script
eg2
0.3.23

prettier-vscode
esb
9.0.0

php-debug
fel
1.22.0

php-cs-fixer
jun
0.2.8

twig-language
mbl
0.9.2

vscode-deploy-reloaded
mkl
0.89.0

vscode-docker
ms-
1.18.0

snippet-creator
nik
0.0.5

vetur
oct
0.35.0

laravel-blade
one
1.28.0

advanced-new-file
pat
1.2.2

vscode-commons
red
0.0.6

vscode-yaml
red
1.2.0

LiveServer
rit
5.6.1

laravel-artisan
rya
0.0.28

code-spell-checker
str
2.0.13

code-spell-checker-russian
str
2.0.1

code-spell-checker-ukrainian
str
0.1.10

tabnine-vscode
Tab
3.5.1

errorlens
use
3.4.1

vscode-import-cost
wix
2.15.0

ascii-unicode-escape
yar
0.1.0

(5 theme extensions excluded)

I have some what same issue when trying to open files from wsl2 or using code-insiders as a core git editor. A new vs code window is opened with a empty new file.

same/similar - current build (and build as of Nov 22) - does not take . or path from code-insiders command line.
With no instances running, first instance opens the first project/location in recent. Subsequent instances open empty.
WSL2 follows this pattern.
Context-menu/right-click in windows context passes correctly to code-insiders (folder or individual file). WSL2 cli does not.
This is true from WSL2 launching with --disable-extensions

I have the same question as you. Why I can use code command to create a new file on Windows but not on Linux?

Perhaps duplicate of #137409 ?

I check it, thank you.

/duplicate
Since this happens on WSL this looks like a duplicate of #137409

authors: cdxn egamma lauritk vystepanenko youfang11523868


text:
integrated terminal tabs on the top or bottom

The current setting terminal.integrated.tabs.location supports only two values, left and right. When using terminal in the panel which is shown on left or right or in the sidebar, when terminal is tall and relatively narrow, this waists space as most of the tall tab column is empty while the terminal itself becomes narrower.
It will be nice if the setting will support also top and bottom values to optimize screen estate usage.

There is this setting, which essentially reverts to the old behavior of a dropdown rather than tabs. Not as good as tabs on top/bottom, but better than eating up 10% of the screen IMO
"terminal.integrated.tabs.enabled": false

Can this issue be re-opened for another round of voting or be opened as a new issue?


text:
Implement "Suggestion Mode" from Visual Studio

In Visual Studio, there is a mode called "Suggestion Mode" that is described here in MS's documentation. This functionality is more succinctly described in this blog post. Basically, I would like for suggestions to be shown, but none "selected" until I actually wish to use them.
This has been brought up in several issues (at the very least #85768, #67698, #33725). I wanted to open a new issue to have the VSCode potentially reconsider this, since after reading one of the VSCode bot's links, it appears that older issues are unsubscribed by the team - it would be great to have this implemented.
Editing with some minor clarifications I provided in my comment below:

The ideal scenario that I personally am trying to have in VSCode is:

I type something into an editor and I get suggestions.
As I get those suggestions, none are "selected" until I hit "tab" or arrow-down the list of suggestions (I personally use "tab" to go through the suggestion list, but the point is that it should be an intentional choice for me to navigate through the list).
At this point, I decide what I want to do. If I intentionally navigate into the suggestion list and I have decided on an item I want to insert, I hit "enter" and VSCode completes the selection into the editor. If I don't navigate into this list, "enter" will just insert a line break.

I’d like to add that from working in Neovim, I found it very intuitive to explicitly select and cycle through auto-completion suggestions with Ctrl + n and Ctrl + p or tabbing then accept with Enter. Currently, I’m resorting to accepting with the Tab key alongside the Vim extension.

does editor.acceptSuggestionOnEnter solve the problem ?

@macintacos does editor.acceptSuggestionOnEnter solve the problem ?

No, it is still selected

I mean it's still selected but enter make a new line, so shouldn't that be good ?

@haoadoresorange no. I still want "enter" to be how completion items are chosen after navigating to them in the list. I just don't want anything in the quick suggestion list selected until I navigate into the list.
The ideal scenario that I personally am trying to have in VSCode is:

I type something into an editor and I get suggestions.
As I get those suggestions, none are "selected" until I hit "tab" or arrow-down the list of suggestions (I personally use "tab" to go through the suggestion list, but the point is that it should be an intentional choice for me to navigate through the list).
At this point, I decide what I want to do. If I intentionally navigate into the suggestion list and I have decided on an item I want to insert, I hit "enter" and VSCode completes the selection into the editor. If I don't navigate into this list, "enter" will just insert a line break.

Hopefully that adds some clarity to this feature request.

@macintacos I see, maybe add this to the original post above ?

Sure, I've updated it.

Isn't that exactly how Visual Studio (the original) works? At least that's what I remember from my VS days. My muscle memory tells me so.

@user72356 VS and VSCode are two different programs.

@user72356 VS and VSCode are two different programs.

So what? You expect people not to compare feature sets when they know something that works better elsewhere? Especially another MS product.

My bad, I misunderstood it as you saying the current functionality is expected, especially since you have a random username.

This actually started with https://github.com/microsoft/vscode/issues/151336

Never thought I'd see the day - this seems to work pretty much exactly the way that I want it to, this is great!
For those who can't be bothered to open that issue, the setting is:
  "editor.suggest.selectQuickSuggestions": false,

It'll present as "disabled", but that appears to be on purpose. It still works.

Actually... not quite. Thought it was working, but it doesn't seem to work the way I have selections set up with my keybindings.
Currently, as stated in the description, I use tab/shift+tab to navigate the suggestion list. This is set up like this:
  {
    "key": "tab",
    "command": "selectNextSuggestion",
    "when": "editorTextFocus && suggestWidgetMultipleSuggestions && suggestWidgetVisible"
  },
  {
    "key": "shift+tab",
    "command": "selectPrevSuggestion",
    "when": "editorTextFocus && suggestWidgetMultipleSuggestions && suggestWidgetVisible"
  }

With "editor.suggest.selectQuickSuggestions": false, the suggestion list isn't selected (great!) but tab doesn't seem to select the first item. Am I just missing a keybind/when-clause/command combination now?

Yeah, there is a new focusSuggestion command which puts focus into the list first. By default it is bound to the trigger keybindings, e.g cmd+space etc. You should be able to configure it.
https://github.com/microsoft/vscode/blob/6e2ee35d1630b4bb916f35fdbd678848d129547c/src/vs/editor/contrib/suggest/browser/suggestController.ts#L884-L895

@jrieken thanks! I'll look into that.
Yeah I'll share what I come up with - I just noticed that it's because it wasn't working when only one item was shown in the suggestion list, because then technically the suggestWidgetMultipleSuggestions would be false in that case (which was causing the default behavior - inserting a tab instead of navigating into the list). Trying to figure it out.

Okay yeah adding this seems to make things work the way I expect:
  {
    "key": "tab",
    "command": "focusSuggestion",
    "when": "editorFocus && suggestWidgetVisible"
  },

Never thought I'd see the day - this seems to work pretty much exactly the way that I want it to, this is great!
For those who can't be bothered to open that issue, the setting is:
  "editor.suggest.selectQuickSuggestions": false,

It'll present as "disabled", but that appears to be on purpose. It still works.

Worked for me, thanks!

👋 Attention: for next Insiders (which will be released after the break) I have renamed the setting to editor.suggest.selectionMode. Also, it is no longer a boolean anymore but allows for more fine grained control when it comes to auto suggest triggered by typing (aka quick suggest) or by trigger-characters.
https://user-images.githubusercontent.com/1794099/209361942-55a68f8b-9fc7-45b2-981c-cf859c46cb72.mov

Closing - remaining work should be tackled as separate bugs or polish issues

authors: BIKA-C Imericxu haoadoresorange jrieken macintacos tristone13th user72356


text:
.bashrc file not loading

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.65.2
OS Version: Chrome OS 99.0.4844.86 (Official Build) (64-bit)

Steps to Reproduce:

open bashrc file with code ~/.bashrc and enter your bash code for terminal, my code is

bind 'TAB:menu-complete'
GREEN=$(tput setaf 051)
TEAL=$(tput setaf 044)
RES=$(tput sgr0)

PS1="\[$TEAL\]<\t> "
PS1+="\[$GREEN\]{\W}"
PS1+="\[$RESET\]$ "
export PS1

how terminal is supposed to look

Open another vscode instance or whatever and open terminal
how terminal looks now

the integrated terminal and this always happens

Cannot repro on Linux:

Could be a Chrome OS problem?

authors: Tyriar ZeroXiphYT


text:
It is not autocompleting my html syntax

I am currently working on a django project but now vs code in not auto completing my html css syntaxes.  for eg h3 is not auto converted to

but it is working completely fine on my other projects

Do you use a Django extension? There are Django extensions that take over the HTML language mode, so the HTML extension is no longer active and you no longer get features like completions.
To test this, run VS Code with all extension disabled and try again.
The expandsion of h3 to

 is driven by emmet. You might solve the problem by configuring emmet.includeLanguages.

authors: aeschli binayak-tech


text:
Duplicate output in devtools when extension writes to process.stdout

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.67.2
OS Version: macOS 12.3.1

Steps to Reproduce:

Write to process.stdout from an extension in development mode.
The output is duplicated in the VS Code developer tools.

extension.ts
// The module 'vscode' contains the VS Code extensibility API
// Import the module and reference it with the alias vscode in your code below
import * as vscode from 'vscode';

// this method is called when your extension is activated
// your extension is activated the very first time the command is executed
export function activate(context: vscode.ExtensionContext) {

	process.stdout.write("Foo\n");

	// Use the console to output diagnostic information (console.log) and errors (console.error)
	// This line of code will only be executed once when your extension is activated
	console.log('Congratulations, your extension "vscode-stdout-bug" is now active!');

	// The command has been defined in the package.json file
	// Now provide the implementation of the command with registerCommand
	// The commandId parameter must match the command field in package.json
	let disposable = vscode.commands.registerCommand('vscode-stdout-bug.helloWorld', () => {
		// The code you place here will be executed every time your command is executed
		// Display a message box to the user
		vscode.window.showInformationMessage('Hello World from vscode-stdout-bug!');
	});

	context.subscriptions.push(disposable);
}

// this method is called when your extension is deactivated
export function deactivate() {}

I would argue this is not a big deal because we provide a debugging and development experience from the debug window in VSCode itself where the output appears normally:

I would argue the devtools window is a nice to have but should not be seen as the main way how to debug an extension.

Well yeah. You do have the output in the debug console as well, and It's just duplicate output, not lost output, so it doesn't really stop you from doing anything, but it's still a bug nonetheless.

authors: bpasero segevfiner


text:
Debugging extensions in codespaces not working

Open a codespace for any extension, for example a vscode-extension-samples folder
Build and run the extension launch config
A tab with this url opens and 404s: https://github.com/codespaces/roblourens-vscode-kusto-grwc?folder=%2Fhome%2Fcodespace&payload=%5B%5B%22extensionDevelopmentPath%22%2C%22vscode-remote%3A%2F%2Fcodespaces%252Broblourens-microsoft-vscode-extension-samples-9vj55ghx599%2Fworkspaces%2Fvscode-extension-samples%2Fcodelens-sample%22%5D%2C%5B%22extensionEnvironment%22%2C%22%7B%7D%22%5D%2C%5B%22debugId%22%2C%22b5379fc5-11b0-418b-a85c-163602e2ebe2%22%5D%2C%5B%22inspect-brk-extensions%22%2C%2253601%22%5D%5D
That url is suspicious, what is roblourens-vscode-kusto-grwc?

I am not sure how extension dev works in codespaces, whose side this would be on, codespaces or us? cc @weinand @connor4312

This looks like codespaces. Nothing has changed on our side.

authors: roblourens weinand


text:
Allow markdown in TreeView#message

I've been trying to implement a simple tree view which dynamically displays whether you are logged in or not (as well as some other buttons in markdown). However, there is no way to render markdown through the TreeView#message api.
You used to be able to render markdown through the TreeView#message api, however, There was an issue which removed the feature.
I am able to render markdown in a tree view by using the "viewsWelcome" field in package.json, however I am unable to use Treeview#message to render markdown.
It would be nice if we could get the ability to render markdown in a TreeView back.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

A case that I'm running into is a filtered tree. The message is a nice way to tell the user that the view is restricted (e.g. "Showing 10 of 15 items"). I'd like to provide a hyperlink to a command to clear the filters.
This behavior is used in the Search view - to provide some additional information about what's being displayed and to provide a hyperlink to perform a related action (e.g. Open in Editor, Open Settings, etc.)

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


text:
手機沒用過這個東西

感謝您創建此問題！
但是，由於描述不是英文的，因此我們很難對其進行處理。如果可以，請將此問題編輯為英文版。請不要添加新評論或創建新問題，而是編輯現有問題。
遺憾的是，自動翻譯服務無法處理有效溝通軟體問題所需的技術語言，因此我們建議您找一位熟悉我們技術的人工翻譯人員來幫助翻譯。
否則，此問題已被標記為需要翻譯，社區成員可能能夠幫助翻譯它。

Thanks for creating this issue!
Unfortunately, as the description is not in English, it's hard for us to work on. If possible, please edit the original issue to be in English.
In our experience, automatic translation services are not able to handle the technical language needed to effectively communicate about software issues, so we recommend finding a human translator who is familiar with our technology to help.
Otherwise, we have marked this as needing translation and a community member may be able to help out.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


text:
Explorer has expand all action enabled

In today's Insiders a74adedba8fb56d14f01f7950340dab33cfeae57.

Expand some folders in the Explorer
Reload

🐛 You see this expand all icon:

Related: https://github.com/microsoft/vscode/issues/155131

Confirmed. The initial status of this button isn't being set correctly after reload. It corrects itself after I expand or collapse any folder in the tree.

@joaomoreno Just an FYI that expand all is expected since it is a heavily requested feature which we pulled in via community PR (although it works a bit weird at the moment due to the async data tree nature of the explorer but I'm not confident in resolving all nodes).

@joaomoreno Just an FYI that expand all is expected since it is a heavily requested feature which we pulled in via community PR (although it works a bit weird at the moment due to the async data tree nature of the explorer but I'm not confident in resolving all nodes).

I didn't say otherwise. But now that you mention it, how are we planning on solving the weird part? The fact that the explorer model is potentially huge and possibly infinite (think recursive FS links) is the reason we never added such an action here in the past. Not saying there isn't community demand (I'm sure there is) but we should create a coherent story and an expand all icon which doesn't "expand all" is misleading. Maybe we should look into addressing the community's pain points in a more surgical way and find better UX affordances that can fix those?

Maybe we should look into addressing the community's pain points in a more surgical way and find better UX affordances that can fix those?

Definitely agree. I'm happy to discuss with anyone who is interested. My initial brainstorm was try to expand a certain set of levels (i.e 5) which would cover most use cases. The biggest pain point with this feature at the moment is that when you initially open a workspace expand all doesn't do anything as we have not resolved any nodes. I will probably hold off shipping this feature in stable until we have a good user story.

authors: gjsjohnmurray joaomoreno lramos15


text:
CMD+[ doesn't reach VS code

Type: Bug
I just got a new computer and I'm trying to use the normal tab navigation keys "shift+CMD+[" and "shift+CMD+]" in VSCode. Right bracket works fine. Left bracket doesn't.
These commands work fine in chrome and other tab based applications. The keybinding debugger shows that "CMD+[" is not reaching VScode.
This issue has been reported before here: https://github.com/microsoft/vscode/issues/114075 but was closed without solution.
VS Code version: Code 1.71.0 (784b0177c56c607789f9638da7b6bf3230d47a8c, 2022-09-01T07:25:25.516Z)
OS version: Darwin arm64 21.4.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
18, 19, 18

Memory (System)
32.00GB (2.48GB free)

Process Argv
--disable-extensions ./ --crash-reporter-id cd13dcc0-10f0-4683-b7a8-aa3c3fc436ee

Screen Reader
no

VM
0%

Extensions disabled
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411cf:30557515
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
pylanb8912:30545647
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012cf:30540253
azure-dev_surveyone:30548225
2144e591:30553903

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

authors: VSCodeTriageBot toppsdown


text:
Signature Help highlighting function name instead of parameter

The bug in signature help occurs when a function has the same name as a parameter. In our case, the function format has two parameters, format and args. Instead of highlighting the first parameter, VS Code highlights the function name.

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.73.0-insider
Commit: a8108049ab61b970f2ec1839dfb753054e07395e
Date: 2022-10-13T05:19:29.769Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin x64 20.6.0
Sandboxed: Yes

Steps to Reproduce:

Create a package.json

{
  "name": "signature-bug",
  "publisher": "Daniel",
  "version": "1.0.0",
  "engines": {
    "vscode": "^1.70.0"
  },
  "activationEvents": [
    "*"
  ],
  "main": "./index.js"
}

Create a index.js

const vscode = require("vscode");

exports.activate = function () {
  console.log(`I am running!`);
  vscode.languages.registerSignatureHelpProvider(
    "*",
    {
      provideSignatureHelp: (doc, pos) => {
        console.log(`providing signature help`);
        const value = new vscode.SignatureHelp();
        value.signatures = [
          {
            label: "format(format, args)",
            parameters: [
              {
                label: "format",
                documentation: "param 1",
              },
              {
                label: "args",
                documentation: "param 2",
              },
            ],
          },
        ];
        value.activeSignature = 0;
        value.activeParameter = 1;
        return value;
      },
    },
    "(",
    ","
  );
};

Run the extension development process
type format( into any buffer/file

I would be happy to take a look at this and submit a PR if you like.

You should use the offset version of the label: https://github.com/microsoft/vscode/blob/182beb6ee4bbed13deabce7ca29f52a30a31824a/src/vscode-dts/vscode.d.ts#L4156
This lets you specify the start and end of the parameter name in the signature help. Otherwise we have to guess where the parameter is based on its index in parameter hint label, which can fail as you are seeing

authors: dbanck mjbvz


text:
If diffEditor.insertedLineBackground or removedLineBackground is overriden, then you cannot see the cursor selection

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.75.1
OS Version: Windows 10 Pro 21H2

Steps to Reproduce:

Go to settings.json and override either insertedLineBackground or removedLineBackground
Open a file within a git repository and check the diff
Make any changes by adding or removing line
Select a removed text or added text. While the cursor selection work, you cannot see the highlighted text

I've tested with both the default and other custom color theme, it seems to occur in all situation. You can see the cursor selection when the color is not overriden

This is another comparison when nothing is selected. The diff lines still have the same color, making it harder to distinguish

This is because the colors are defined without any transparency. The solution is to use opacity in the colors you define. e.g. #08310088. @aeschli Could there be a way to show a squiggle if opacity is not used in some colors?

Thanks @alexdima . I can confirm setting the opacity lower would show the cursor selection. I can also see the squiggle if opacity is not set.

authors: Skarvion alexdima


text:
Add Warn Before Quitting / Close window

Motivation
I sometimes accidentally quit VSCode by pressing cmd + q / close VSCode window while deleting tabs.
In order to avoid the accidents,  Having Warn Before Quitting / Close window feature would be great like Chrome or FireFox.

The setting is called: window.confirmBeforeClose

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


text:
color bug

Type: Bug
Why are the characters coming in different colors at the same line?
VS Code version: Code 1.78.2 (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T14:39:26.248Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 7 5800H with Radeon Graphics          (16 x 3194)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.36GB (8.58GB free)

Process Argv
--crash-reporter-id 70259e21-03d7-4dea-a6d9-4cb2f064bb39

Screen Reader
no

VM
0%

Extensions (37)

Extension
Author (truncated)
Version

vscode-html-css
ecm
1.13.1

code-runner
for
0.12.0

c-cpp-runner
fra
5.4.0

isort
ms-
2022.8.0

python
ms-
2023.8.0

vscode-pylance
ms-
2023.5.30

jupyter
ms-
2023.4.1011241018

jupyter-keymap
ms-
1.1.0

jupyter-renderers
ms-
1.0.15

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

cmake-tools
ms-
1.14.31

cpptools
ms-
1.15.4

cpptools-extension-pack
ms-
1.3.0

sqltools
mtx
0.27.1

java-extension-pack-jdk
Ple
2023.515.0

sqlite-viewer
qwt
0.2.5

java
red
1.18.0

vscode-community-server-connector
red
0.26.10

vscode-rsp-ui
red
0.24.5

LiveServer
rit
5.7.9

open-in-browser
tec
2.0.0

pdf
tom
1.2.2

cmake
twx
0.0.17

vscode-lldb
vad
1.9.1

intellicode-api-usage-examples
Vis
0.2.7

vscodeintellicode
Vis
1.2.30

vscode-boot-dev-pack
vmw
0.2.1

vscode-spring-boot
vmw
1.46.0

vscode-gradle
vsc
3.12.7

vscode-java-debug
vsc
0.50.0

vscode-java-dependency
vsc
0.22.0

vscode-java-pack
vsc
0.25.11

vscode-java-test
vsc
0.38.2

vscode-maven
vsc
0.41.0

vscode-spring-boot-dashboard
vsc
0.13.0

vscode-spring-initializr
vsc
0.11.2

(3 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
2e4cg342:30602488
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
showlangstatbar:30737416
vsccsb:30705552
azdwalk:30721579
pythonms35:30701012
24365598:30736109
pythonfmttext:30731395
fixhidewlkth:30730051
pythongtdpath:30739704

/gifPlease
/needsMoreInfo

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


text:
not opening

Type: Bug
vscode suddenly getting slow &slowy opening in my pc,windows  are updated,getting white screen while opening
VS Code version: Code 1.78.2 (b3e4e68a0bc097f0ae7907b217c1119af9e03435, 2023-05-10T14:39:26.248Z)
OS version: Windows_NT x64 6.0.6002
Modes:
Sandboxed: Yes

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: unavailable_software

Load (avg)
undefined

Memory (System)
7.70GB (1.69GB free)

Process Argv
--crash-reporter-id 51df6a0a-a68a-4a3b-880e-8a1b7f315e7b

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

code-runner
for
0.12.0

vscode-test-explorer
hbe
2.21.1

python
ms-
2023.8.0

vscode-pylance
ms-
2023.5.40

powershell
ms-
2023.5.0

test-adapter-converter
ms-
0.1.7

java
red
1.18.0

LiveServer
rit
5.7.9

intellicode-api-usage-examples
Vis
0.2.7

vscode-java-debug
vsc
0.51.0

vscode-java-dependency
vsc
0.23.0

vscode-java-test
vsc
0.39.0

vscode-maven
vsc
0.41.0

php-debug
xde
1.32.1

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30610678
282f8724:30602487
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
pythonfmttext:30731395
fixhidewlkth:30730051
hidesbindicator:30730055
pythongtdpath:30739704

not opening vs code


text:
vscode plugin webview support copy/paste in iframe

I think this is a duplicate of #129178

Two years later, this problem still exists, this problem is too hard...

/duplicate

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


text:
[Accessibility] Verified domain in Extension page doesn't have a clear title attribute

Currently, the Verified domain: http://example.com only show as http://example.com, which make it hard for screen readers to understand its meaning.

In contrast, other icons and texts are well-labelled and easy to understand.

It would be nice to give Verified domain a proper accessibility attribute.

Hi, I think I have found a fix for this. However I was wondering if someone could provide some insight into what the best way to validate my fix would be considering the extension marketplace is not available on the test environment. Thanks!

@amaust you can create a PR and I can test it. Or you can install an extension by downloading it and then clicking install via .vsix in the overflow menu of the extensions view

I'll try downloading an extension and trying it that way and if I can't get that to work I'll submit a PR. Thanks!

authors: Young-Lord amaust meganrogge


text:
improve discoverability of accessibility info in copilot experience

Screen reader users learn about accessibility features related to the copilot experience via accessibility help, which is discoverable in the aria label of the input box.
Low vision users, keyboard only users, and others might not discover this.
We should consider adding a button/link to the Copilot welcome message so all users can learn about the accessibility features.

Can we instead mention it in our Copilot docs on our website?
https://code.visualstudio.com/docs/editor/github-copilot#_chat-features
Since the Copilot welcome message already links there?
@gregvanl for thoughts?

Yes, I wondered about that. But I think we'd need to include them very close to the top, if so?

The fable study showed that magnification users aren't aware of the accessible view, which would help when keyboard shortcut labels wrap. They would also benefit from the accessibility help dialog, which provides an overview of what to expect with the chat experience.

I'm not convinced we should put more text in the welcome message, given we invested effort to trim it down lately. Should we rather make sure that the accessible view and accessible help functionality are discoverable (maybe in our Get Started walkthrough and our documentation)?

As long as the accessibility information is placed prominently in our documentation, that sounds good to me.

Increasingly various parts of VS Code have onboarded to the accessibility help, would we consider also moving mention of the accessibility help higher in the accessibility documentation to help with this? https://code.visualstudio.com/docs/editor/accessibility#_accessibility-help

I have moved accessibility help up in our docs.
I don't think we necessarily need to add it to the Copilot documentation. I'll keep getting feedback on this.

authors: isidorn joyceerhl meganrogge


text:
Changing the UI font

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

authors: VSCodeTriageBot abhiramakella


text:
High CPU Usage Code Helper (Renderer)

Type: Bug
Open VScode and see your CPU Usage

VS Code version: Code 1.87.0 (019f4d1419fbc8219a181fab7892ebccf7ee29a2, 2024-02-27T23:42:51.279Z)
OS version: Darwin arm64 23.2.0
Modes:

System Info

Item
Value

CPUs
Apple M1 Pro (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
6, 5, 4

Memory (System)
32.00GB (5.80GB free)

Process Argv
--crash-reporter-id 6400a2ea-63e2-4f84-a4ed-22d915a4b18d

Screen Reader
yes

VM
0%

Extensions (73)

Extension
Author (truncated)
Version

vscode-base64
ada
0.1.0

sort-imports
ama
6.3.1

vscode-symlink
anb
0.0.3

package-json-upgrade
cod
2.1.2

vscode-mysql-client2
cwe
6.9.5

dart-code
Dar
3.80.0

flutter
Dar
3.80.0

vscode-eslint
dba
2.4.4

xml
Dot
2.5.1

gitlens
eam
14.7.0

prettier-vscode
esb
10.1.0

opensslutils
ffa
1.1.1

vscode-jest-runner
fir
0.4.72

vscode-sql-tagged-template-literals-syntax-only
fri
0.0.19

kotlin
fwc
0.2.34

codespaces
Git
1.16.8

copilot
Git
1.155.0

copilot-chat
Git
0.11.1

vscode-pull-request-github
Git
0.79.2024011609

go
gol
0.40.3

vsc-nvm
hen
0.0.3

vscode-edit-csv
jan
0.8.3

x509-parser
jlc
0.0.6

vscode-graphviz
joa
0.0.6

svg
joc
1.5.3

solidity
Jua
0.0.165

vscode-gutter-preview
kis
0.30.0

lit-snippets
lit
1.0.2

vscode-lottie
lot
1.0.5

kubernetes-templates
lun
1.3.1

regionfolder
map
1.0.22

rainbow-csv
mec
3.11.0

vscode-language-babel
mgm
0.0.40

git-graph
mhu
1.30.0

dotenv
mik
1.0.1

vscode-docker
ms-
1.28.0

vscode-kubernetes-tools
ms-
1.3.15

isort
ms-
2023.10.1

python
ms-
2023.22.1

vscode-pylance
ms-
2023.12.1

jupyter
ms-
2023.11.1100101639

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

remote-containers
ms-
0.327.0

remote-ssh
ms-
0.107.1

remote-ssh-edit
ms-
0.86.0

remote-explorer
ms-
0.4.1

remote-server
ms-
1.5.0

vsliveshare
ms-
1.0.5905

vscode-json-editor
nic
0.3.0

indent-rainbow
ode
8.3.1

kubernetes-context
Okt
0.1.0

material-icon-theme
PKi
4.33.0

prisma
Pri
5.8.1

quicktype
qui
12.0.46

sqlite-viewer
qwt
0.3.13

vscode-thunder-client
ran
2.17.1

vscode-yaml
red
1.14.0

lit-plugin
run
1.4.3

swift-lang
ssw
1.7.2

graphviz-interactive-preview
tin
0.3.5

lorem-ipsum
Tyr
1.3.1

errorlens
use
3.16.0

vscode-lldb
vad
1.10.0

vscodeintellicode
Vis
1.2.30

vscode-swiftformat
vkn
1.6.7

fig
wit
0.0.7

pretty-ts-errors
Yoa
0.5.3

save-as-root
yy0
1.8.0

markdown-all-in-one
yzh
3.6.2

chat-gpt
zha
1.6.63

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:30968133
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfcontrol:30979541
d34g3935:30971562
edj9j583:30969295
fegfb526:30973843
bg6jg535:30979843
78248357:30976999
dsvsc020:30976470

App extensions is the problem

Which extension was the problem? I am experiencing the same issue after VSCode update

authors: domnantas herberthobregon


text:
Show progress while resolving next level hover

Testing #210904
When a hover provider takes a few seconds to resolve the next level hover, there is not currently any feedback that next hover is being resolved. I suggest we show a spinner and also prevent the user from clicking the +/- buttons in these cases

The hover verbosity logic has been changed so that it is now possible to make consecutive requests while a request is still pending in https://github.com/microsoft/vscode/pull/213317. This will end the current request and start a new request. With this logic, the + and - buttons need to be enabled.
We could still consider adding a loading spinner however to show that work is done. I am not sure however where to place it. Indeed there is little space in the hover. The hover can be of variable size - as tall as the height of 1 line for example (19 pixels only), so there isn't vertical space where to place the spinner. We could place the spinner to the left or to the right of the +/- icons but that could look a bit strange, as the hover expands horizontally to accomodate a spinner and then contracts when loading is finished.

authors: aiday-mar mjbvz


text:
Saving any files takes too long

Type: Performance Issue
Hi Team,
Recently observed that it is taking too much time to save any file. The below message keeps occuring everytime I do cmd+S.

Please Note : I am using format on save option.
Below is my settings.json file.
"[python]": {         "editor.defaultFormatter": "charliermarsh.ruff",         "editor.formatOnPaste": false,         "editor.formatOnSave": true,         "editor.formatOnType": true,         "editor.codeActionsOnSave": {             "source.fixAll.ruff": "explicit",             "source.organizeImports.ruff": "explicit"         }     }, "editor.codeActionsOnSave": {         "source.fixAll": "explicit",         "source.organizeImports": "explicit"     },
VS Code version: Code 1.89.1 (Universal) (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:14:24.611Z)
OS version: Darwin x64 23.4.0
Modes:
Connection to 'tunnel+ci-va2-remote' could not be established

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
2, 3, 3

Memory (System)
16.00GB (0.31GB free)

Process Argv
--crash-reporter-id 4e1a7f74-58fc-4b9a-bed4-13f7d0786d16

Screen Reader
no

VM
0%

Connection to 'tunnel+ci-va2-remote' could not be established

Process Info
CPU %	Mem MB	   PID	Process
    9	   213	   658	code main
    4	    66	   699	   gpu-process
    0	    33	   700	   utility-network-service
    0	   213	   714	window [2] (cron.sh — core-platform-scripts-php [ci-va2-remote] — pytest automation)
    3	   475	   716	window [4] (test_debug_creation_request.py — UnifiedAPIFramework — pytest automation)
    0	    98	   817	shared-process
    0	     0	 55877	     /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	    82	   820	extensionHost [2]
    0	    33	 47313	     electron-nodejs (proxyServer.js )
    0	    33	   825	fileWatcher [2]
    0	    33	   834	ptyHost
    0	     0	 48810	     /bin/zsh -i
    0	     0	 48873	     /bin/zsh -i
    1	   901	 48783	extensionHost [4]
    0	    49	 48854	     /usr/local/Cellar/python@3.11/3.11.8/Frameworks/Python.framework/Versions/3.11/Resources/Python.app/Contents/MacOS/Python /Users/saurabhrai/.vscode/extensions/charliermarsh.ruff-2024.20.0-darwin-x64/bundled/tool/server.py
    0	   705	 48906	     electron-nodejs (bundle.js )
    0	   115	 48980	     /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) /Users/saurabhrai/.vscode/extensions/streetsidesoftware.code-spell-checker-3.0.1/packages/_server/dist/main.cjs --node-ipc --clientProcessId=48783
    0	   180	 48985	     /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/jre/21.0.3-macosx-x86_64.tar/bin/java -jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/server/sonarlint-ls.jar -stdio -analyzers /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonargo.jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonarjava.jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonarjs.jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonarphp.jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonarpython.jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonarhtml.jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonarxml.jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonarcfamily.jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonartext.jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonariac.jar /Users/saurabhrai/.vscode/extensions/sonarsource.sonarlint-vscode-4.5.1-darwin-x64/analyzers/sonarlintomnisharp.jar
    0	    49	 48784	fileWatcher [4]
    0	   131	 53227	   window
    2	    66	 55831	window [5] (Issue Reporter)
Connection to 'tunnel+ci-va2-remote' could not be established

Workspace Info
|  Window (test_debug_creation_request.py — UnifiedAPIFramework — pytest automation)
|    Folder (UnifiedAPIFramework): 11702 files
|      File types: log(6738) json(1983) pyc(923) py(861) csv(114) tsv(66)
|                  xlsx(53) md(35) DS_Store(29) txt(22)
|      Conf files: launch.json(1) settings.json(1) tasks.json(1)
|      Launch Configs: debugpy(2)
Connection to 'tunnel+ci-va2-remote' could not be established;

Extensions (41)

Extension
Author (truncated)
Version

ruff
cha
2024.20.0

dbclient-jdbc
cwe
1.3.5

vscode-database-client2
cwe
4.5.12

vscode-eslint
dba
2.4.4

gitlens
eam
14.9.1

nasc-touchbar
fel
1.12.0

copilot
Git
1.190.0

copilot-chat
Git
0.15.1

vscode-pull-request-github
Git
0.88.1

gc-excelviewer
Gra
4.2.59

rainbow-csv
mec
3.11.0

vscode-docker
ms-
1.29.1

dotnet-interactive-vscode
ms-
1.0.5229040

debugpy
ms-
2024.6.0

python
ms-
2024.6.0

vscode-pylance
ms-
2024.5.1

jupyter
ms-
2024.4.0

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.9

vscode-jupyter-powertoys
ms-
0.1.1

vscode-jupyter-slideshow
ms-
0.1.6

remote-containers
ms-
0.362.0

remote-ssh
ms-
0.110.1

remote-ssh-edit
ms-
0.86.0

vscode-remote-extensionpack
ms-
0.25.0

remote-explorer
ms-
0.4.3

remote-server
ms-
1.5.1

test-adapter-converter
ms-
0.1.9

vsliveshare
ms-
1.0.5918

vsliveshare-pack
ms-
0.4.0

vs-sequential-number
nep
1.1.0

material-icon-theme
PKi
5.2.0

postman-for-vscode
Pos
1.0.1

vscode-yaml
red
1.14.0

LiveServer
rit
5.7.9

jenkins-jack
sau
1.0.1

vscode-fileutils
sle
3.10.3

sonarlint-vscode
Son
4.5.1

code-spell-checker
str
3.0.1

vscode-icons
vsc
12.7.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
tftest:31042121
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
vscrp:30673768
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:31000449
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
showvideot:31016892
dsvsc021:30996838
9c06g630:31013171
88717513:31044517
dwnewjupytercf:31039676

Please use the Start Extension Bisect command to investigate whether the problem is being caused by one of your extensions

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


text:
Easier Add all missing imports

Type: Feature Request
Allow Add all missing imports as a separate command without forcing cursor to be on top of an unimported symbol
VS Code version: Code 1.90.2 (5437499feb04f7a586f677b155b039bc2b3669eb, 2024-06-18T22:54:35.075Z)
OS version: Darwin arm64 23.5.0
Modes:

There's a already a source action for this:

You can even setup a keybinding using editor.action.sourceAction if you'd like

authors: mjbvz ravshansbox


text:
Error code 174979597

Hey!
I was watching the 1st course and during the "Meow" section I pressed the wrong key because it kept write meow over and over and wouldn't stop. Making it impossible to stop it, clear, etc. I refreshed the page, but it went straight to meow and repeating 'meow.' Closed the tap and now when I go to the cs50.dev site and this is what pops up.
"Unable to open '174979597'
Unable to resolve resource vscode-remote://codespaces%2Bfriendly-space-yodel-v6gww55x6pxpcx7xj/workspaces/174979597"
Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
Embedder: codespaces

Please reach out to your course support personnel.


text:
Language-c no-colorize case

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: Version: 1.92.2 (user setup)
OS Version: Windows 11 23H2 22631.4037

Steps to Reproduce:

coding like these: bug case:

normal case 1:

normal case 2:

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Can you share a copy/pastable snippet that I can use to reproduce the issue?

Can you share a copy/pastable snippet that I can use to reproduce the issue?

yes, same as the content in pictures:
bug case:
`#if 0 //xxxxxxx
do_something(argu); //xxxxxx
#endif
if(A==B)
{
for(i=0;i<k;i++)
{
do_somethingB();
}
}
`
normal case 1:
`#if 0
do_something(argu); //xxxxxx
#endif
if(A==B)
{
for(i=0;i<k;i++)
{
do_somethingB();
}
}
`
normal case 2:
`#if 0 //xxxxxx
#endif
if(A==B)
{
for(i=0;i<k;i++)
{
do_somethingB();
}
}
`
I can add one more situation that the code behind macro can be colorized normally.
normal case 3:
`#if 0 //xxxxxx
do_something(argu); //xxxxxx
#endif
if(A==B)
{
for(i=0;i<k;i++)
{
do_somethingB();
}
}
`

Thank you! Duplicate of upstream issue: https://github.com/jeff-hykin/better-c-syntax/issues/4


text:
Can we have a better mouse to caret positioning?

VSCode Version: Code 1.16.1 (27492b6bf3acb0775d82d2f87b25a93490673c6d, 2017-09-14T16:38:23.027Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

I know this convention is half one way, half the other...
For as long as text editors have existed there has been 2 conventions on mouse to caret positioning
One, which is what Code used now, is the annoying clicking anyway on a character places the caret in front of the character (Notepad)
The other, better imho, is if you click on a character, which ever side of the character, the left or the right, the mouse is, that is where the caret will be placed. (Notepad ++, this one seem to place the caret to the front clicking on the left 2/3rd of the character and to the back clicking the right 1/3rd). Which reduces the selection error quite drastically.
Is there a way to set that up in the settings?

Extension
Author (truncated)
Version

vscode-autohotkey
sle
0.2.1

Steps to Reproduce:

Reproduces without extensions: Yes/No

Any, um, updates on this?? From what I've noticed, current behavior is that clicking left 2/3 of the character positions caret before. Could we make this 1/2? This trips me up and slows me down quite a bit sometimes when my hand is tired.
Yeah, I know. True programmers don't use the mouse.


text:
Incorrect Indentation

VSCode Version: 1.25.0
OS Version: Windows 10

The following are a few of the instances i noticed incorrect indentation. I hope i don't have to debate why they're incorrect:

case xxxx:
The next line starts immediately under 'c' and not indented.

object.function(param1,
The next line starts with no indentation

this.function(param1,
param2 );
Pressing enter after the semicolon starts the next line right under 'p' which is incorrect. Indentation is not reset here.

if(some condition)
Next line is not indented if I don't use paranthesis. With paranthesis the indentation is correct.

for(...)
Same as for "if". If I don't use paranthesis the indentation is not happening otherwise it's ok

When does the incorrect indention occur? After format or just when typing?

To explain step 4:
With parenthesis automatic indentation works:
if (hello === 'world') {
    helloWorld();
}

Without parenthesis automatic indentation doesn't work:
if (hello === 'world')
helloWorld();

Fixing of this bug would possibly be the lowest hanging fruit to improve coding experience in VS Code.

Closing due to lack of further user interest expressed in this issue over the past two plus years
(also please open separate issues for problems like this in the future to make them more discoverable)

authors: jeffsaremi mjbvz touho


text:
"Accept all Current/Incoming" does not work when selecting multiple files (in Source Control Tab)

VSCode Version: 1.29.1
OS Version: Windows 10 / Ubuntu 16.04

Steps to Reproduce:

git rebase a repo
select more than one file with conflicts
right click selected files and do "Accept all Incoming" or "Accept all Current"
I would assume that this affects all selected files, not just one

Does this issue occur when all extensions are disabled?: Yes

I have 50+ files in merge conflicts. Missing this is a big deal. 😛

Seeing the same issue.
Similar / related:

git rebase repo
right click file with conflicts without left-click / opening file in editor pane
click "Accept all Incoming" / "Accept all Current"
no changes are accepted, file in list remains unchanged.

Same here, I have 60+ files, this fix would be greatly appreciate it!

Even if you couldn't do it all at once it would be helpful to have these options:
"Accept all current and Save"
"Accept all incoming and Save"
Right now you have to do them one at a time and save them in the file pane too.

Git might help (see all top rated answer): https://stackoverflow.com/questions/10697463/resolve-git-merge-conflicts-in-favor-of-their-changes-during-a-pull

It would be nice to do this from the ui though, as that would allow bulk merging of most files, and then manual handling of the rest.
It's also nice to resolve merge conflicts following the usual workflow, rather than having to use a different workflow for specific edge cases

@chrmarti in this case, that Git command is not quite what I was looking for.  I wanted to manually merge a few files and then accept the rest.
I thought I could highlight a group under Merge changes and click Accept All Incoming, since this is how Stage Changes and Unstage Changes work.  But Accept All ... only seems to apply for one file at at time (that is, the first one you clicked on).

I have Accept incoming changes but it looks like it does Accept current changes
Can somebody clarify which of them for the changes made locally?

It not only not affects many files when you have them selected... You also have to left click on the new file you want to affect and then right click. So, for example if you have file-A selected by clicking on it with the left mouse button and then you directly right click on file-B the action you perform will still affect file-A

Correct, this is annoying; in addition you have to SAVE the file after choosing accept all incoming.
So current workflow with merge conflicts; every file has to be selected by left-clicking, then right-clicking, choosing 'accept incoming' for example. You have to SAVE the file before you can "+" it.
Suggested workflow;
Select multiple files, right-click; accept incoming
Should do just that, save the files and add them to the staged changes

Fixed for July. Note that you still need to save, but can enable Auto Save to avoid that.

Thnx @chrmarti :-)

authors: EmandM FanrayMedia StephenKoller Webunity brcrista chrmarti daffodil2021 danielo515 jimthedev t0lkman unional


text:
Can't open new window on separate desktop (macOS) if there are windows on other desktops

VSCode Version: 1.29.1 and 1.30.0-insider
OS Version: macOS 10.14 (18A391)

Steps to Reproduce:

Open VSCode in Desktop 1
Move to Desktop 2
"New Window (Cmd+Shift+N)" won't work
Right click the icon in the Dock -> "New Window" will instead work

Gif showing the bug: https://duaw26jehqd4r.cloudfront.net/items/1V0c0V0k3w3d313a2b1m/Screen Recording 2018-11-29 at 01.29 AM.gif

Does this issue occur when all extensions are disabled?: Yes

The problem described in #35240 is similar but not the same (in that case it focuses on the existing virtual desktop).

I wonder if this is the same thing as something I've been seeing:

Run VS.code.
Create a window.
Minimise to the dock (with the yellow traffic-light icon in the window).
Press Shift-Cmd-N to create another new window.

EXPECTED: The new window appears.
ACTUAL: Nothing happens.

Yep, can confirm that happens too. Probably related. Thanks!

As a workaround I created an Automator application called "VSCode New Window" that runs a "Shell Script" (one of the available actions in Automator) with the command /usr/bin/local/code -n.

Still an issue on VSCode 1.34.0 / macOS 10.14.4.
Besides "New File", it cannot "Open...", "Open Workspace...", etc. "Open Recent..." opens a window but it will jump to another space, which is not desirable.

Still an issue on VSCode 1.35.1 / macOS 10.14.5

Still an issue on VSCode 1.42.0 / macOS 10.15.3

Still an issue on VSCode 1.43.2 / macOS 10.15

Still an issue on VSCode 1.44 / macOS 10.15.4

Still an issue on
Version: 1.47.0-insider
Commit: 9bf6af04dcb5c2e531cedca83cd188939ca1b0db
Date: 2020-06-26T21:11:02.609Z
Electron: 8.3.3
Chrome: 80.0.3987.165
Node.js: 12.13.0
V8: 8.0.426.27-electron.0
OS: Darwin x64 19.5.0

Why was this closed?  I think people are commenting and replying to this issue (for years) to explicitly let the team that this hasn't been fixed.  Or possibly people have been replying so it doesn't get lost or be assumed to be fixed with Mac updates, library updates or other passive luck.
Is it a wontfix or just too mysterious, related to Electron or some other fundamental technology that it has become cantfix?

I think it's been closed because it's been fixed. This commit was merged to master early today https://github.com/microsoft/vscode/commit/6dc0327c9af20d0dfe7112feed7c4f75d32b0e83 🎉🎉🙏 Thank you team!

The unreleased tag should be updated when the fix ships in insiders in the coming days.

I think it's been closed because it's been fixed. This commit was merged to master early today 6dc0327 🎉🎉🙏 Thank you team!

Oh, I see!  I missed the SHA/commit.  Sorry.  🙂

authors: SamWolski bzmillerboy chpmrc jlarcombe kkew3 rlab robderon robenkleene sbatten squarism wmayner


text:
SyntaxError: invalid regexp group

I'm trying to ship the standalone editor and it is not coming up in FF or Edge due to the following regular expressions:
https://github.com/Microsoft/vscode/blob/52306b406d9231a0667c758e536bd177e5570180/src/vs/base/browser/ui/menu/menu.ts#L23-L24
I will push a workaround to the standalone/0.16.x branch, but can you please tweak your regular expression such that it works also on Edge and FF? Thanks!

Marking as web as this is something we should revisit eventually when supporting other browsers.
cc @sbatten

@bpasero Why did the importance level drop? This blocks the release of the editor...

@alexandrudima my understanding is that you pushed a workaround for this issue (try-catch) that unblocks the release of the editor. For example, I can see releases that date to after this issue was created:

I think we should use important labels for stuff like data loss etc. but not if a workaround is installed. Nevertheless I agree we should fix this asap.

I didn't do 0.17.0

Yeah you are right, sorry for that :heart:

authors: alexandrudima bpasero


text:
Path delimiters in ${workspaceFolder} and friends ...

VS Code is a marvellous piece of work. Thanks.
One small feature request: It would be very useful to specify which path characters (/ or \) were used when expanding macros such as ${workspaceFolder}.
The current default can be problematic in some scenarios - https://github.com/microsoft/vscode-cpptools/issues/3627
Thanks for listening.

Path delimiters in variables like ${workspaceFolder} are defined by the OS where the folder is located.
In your case the path starts with the drive letter "R:" which confirms that the path is a Windows path.
Why would a tool that can deal with drive letters choke on backslashes?
I think that the backslash issue needs to be fixed where it happens.


text:
Use variables inside tasks.json inputs config

I'd love to be able to create an input variable in tasks.json which defaults to a predefined variable:
"inputs": [
  {
    "type": "promptString",
    "id": "filePath",
    "description": "Enter file path",
    "default": "${relativeFile}"
  }
]

however currently the default is literally ${relativeFile}

Duplicate of #64358


text:
Terminal text processing is broken

Issue Type: Bug

Type a long string without hitting new line.
When characters overflow beyond the visible range for a line, we hit the following error (Seems to be broken after the recent update):

An error occurred while reading input:
System.ArgumentOutOfRangeException: The value must be greater than or equal to zero and less than the console's buffer size in that dimension.
Parameter name: top
Actual value was 22.
at System.Console.SetCursorPosition(Int32 left, Int32 top)
at Microsoft.PowerShell.EditorServices.Console.ConsoleReadLine.InsertInput(StringBuilder inputLine, Int32 promptStartCol, Int32 promptStartRow, String insertedInput, Int32 cursorIndex, Int32 insertIndex, Int32 replaceLength, Int32 finalCursorIndex)
at Microsoft.PowerShell.EditorServices.Console.ConsoleReadLine.d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerShell.EditorServices.EditorServicesPSHostUserInterface.d__95.MoveNext()
VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:35:15.005Z)
OS version: Windows_NT x64 10.0.18980

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz (8 x 3408)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.79GB (11.87GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

code-gnu-global
aus
0.2.2

scratchpad
awe
0.1.0

unique-lines
bib
1.0.0

gitlens
eam
10.0.1

vscode-nmake-tools
Mic
2.0.190920005

python
ms-
2019.9.34911

cpptools
ms-
0.25.1

csharp
ms-
1.21.3

powershell
ms-
2019.9.0

team
ms-
1.149.2

partial-diff
ryu
1.4.0

code-spell-checker
str
1.7.18

shell-launcher
Tyr
0.3.0

vscode-icons
vsc
9.4.0

/duplicate https://github.com/microsoft/vscode/issues/78967

authors: Tyriar vikrampraveen


text:
Feature: Refactor all fs.readdir calls so that the api matches the new openDir iterator

NodeJS > 12.11.1 will have async readdir support Landed in cbd8d71 ( https://github.com/nodejs/node/commit/cbd8d715b2286e5726e6988921f5c870cbf74127 ) as fs{Promises}.opendir(), which returns an fs.Dir, which exposes an async iterator.
This will allow us to open big directorys without issues.
first step would be identify all places that do the old readdir calls and refactor them to use iterators till we switch to node > 12.11.1 when we then have switched we can simply replace the function name and are ready.

@frank-dspeed there is more to it than just using this new method right? If a component requires all children of a folder to be resolved, we would still need to iterate over all children right?
In other words: if this new API is so efficient, I would expect fs.readdir to also use that API under the hood.

@bpasero the main problem with fs.readdir is that it reads all befor it returns the new api can return while reading.

@frank-dspeed understood, but in most cases where we call fs.readdir we actually need all the children (e.g. copy them over into some of our data structures like the file explorer). Do you have a concrete example where we should use this new API

@bpasero  https://github.com/Microsoft/vscode/issues/43838
we need it at last in the file explorer and general even if we copy over structures we can do that incremental we will never whant to wait for 1 mio directorys to be loaded complet we can process each item

@frank-dspeed are you speculating or have a real world example where VSCode today is slow handling this?

@bpasero i will prepare a demo no problem its a general nodejs problem not related to vscode alone i will prepare a demo project to open then you can play around with it

OK

@bpasero i have verifyed it a bit but i used a big Ram disk as i have only ssd drives here and they would get killed to fast.
Example Demo Project
# Lets Create half million entrys
mkdir -p ~/project/src/module{1.5000000}/{1..2}

Open it even from a ram drive on a big i9 machine this took me a minut till it got responsiv.
When this gets opened on a laptop you can get a coffe in that time. (Starbucks one not the one from the local coffe machine )

The file IO layer can provide this iterator but that is not the hard task. Adopting this e.g. in the explorer to scale well is the real work. We can explore once we get access to the API, which is likely 6-9 months out given Electron is behind.

Related: https://github.com/microsoft/vscode/issues/81473

I've tested opendir in readdirp and commented in the issue.
Good news: we can speed up walking the filesystem walk 3x compared to current version by using dirent with node 10.x+.
Bad news: opendir is shit, it will slow down the process by 300%.

@paulmillr you don't understand it correct the issu is not the speed till fully readed the case here is that there are directorys with files more then 100k and we need to stay responsiv.
Goal here is

Reduce time till first entry is emmited.

Addition only for documentation
The fastest dir listing with minimum resource usage is parsing a nodeStream of spawn find(posix) that supports backpressure and also don't needs to wait till fully read.
but openDir will improve soon at present its the libuv2 binding and its only the first version of the code.

I understand the issue fully, it’s just we should not switch to new apis until they are polished. In this case, it’s 3x slower. They’re improving the perf right now. Let’s see how it works out.

authors: bpasero frank-dspeed paulmillr


text:
Some dates in front matter (yaml) are not being marked as timestamps

---
a: b
a: 2019-10-1
a: 2019-10-10
---

Version: 1.41.0-insider (user setup)
Commit: 27cd33d891eb23e370b672e751be9fe8b3748ac1
Date: 2019-11-08T19:12:35.358Z
Electron: 6.1.4
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18362

Moved to owning repo: https://github.com/microsoft/vscode/issues/84435


text:
When staging changes on Source Control, all closed Git repositories are opened again

Issue Type: Bug

Open a folder with multiple Git Repositories
Close some repositories
Change 1 file on an open repository
Stage change

When refreshing git status, all git repositories are re-opened
VS Code version: Code - Insiders 1.41.0-insider (2014f5adccbce83d347e714206903f2bbee40dcb, 2019-11-18T09:37:06.552Z)
OS version: Linux x64 5.0.0-36-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (4 x 2764)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: unavailable_offviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
11.59GB (0.58GB free)

Process Argv
--no-sandbox --unity-launch

Screen Reader
no

VM
0%

Extensions (28)

Extension
Author (truncated)
Version

vscode-tomcat
ada
0.11.1

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

bracket-pair-colorizer
Coe
1.0.61

gitlens
eam
10.2.0

vsc-material-theme
Equ
30.0.0

prettier-vscode
esb
3.8.0

search-node-modules
jas
1.3.0

node-module-intellisense
lei
1.5.0

dotenv
mik
1.0.1

vscode-postgresql
ms-
0.2.0

Go
ms-
0.11.9

typescript-javascript-grammar
ms-
0.0.53

vsliveshare
ms-
1.0.1293

vscode-boot-dev-pack
Piv
0.0.8

vscode-concourse
Piv
1.13.0

vscode-manifest-yaml
Piv
1.13.0

vscode-spring-boot
Piv
1.13.0

material-icon-theme
PKi
3.9.1

java
red
0.53.1

vscodeintellicode
Vis
1.2.0

vscode-java-debug
vsc
0.23.0

vscode-java-dependency
vsc
0.6.0

vscode-java-pack
vsc
0.8.0

vscode-java-test
vsc
0.21.0

vscode-maven
vsc
0.19.1

vscode-spring-boot-dashboard
vsc
0.1.6

vscode-spring-initializr
vsc
0.4.6

Possibly a duplicate of #85247

Well, I'm not sure if it's an exact duplicate, but the issue appears to be related

Close some repositories

How do you close them?

authors: KevLehman gjsjohnmurray joaomoreno