text:
Switch workspace setting file from JSON to HJSON

HJSON is a better format for JSON files that are meant to be edited/used by humans. Let's use it instead of JSON.

Yaml was also suggested in #4851, which has an explanation of why we're using JSON.

HJSON is not YAML. It's fully backward compatible with JSON.

Hjson is a syntax extension to JSON. It's NOT a proposal to replace JSON or to incorporate it into the JSON spec itself. It's intended to be used like a user interface for humans, to read and edit before passing the JSON data to the machine.

I know, I just mean that YAML has also been suggested, and the arguments are the same.

I'm not sure the same arguments against YAML really apply here.

There is a native parser built into the runtime and we care deeply about parsing speed. For example, we parse configuration files during startup.

There is an HJSON parser npm package you can use. Optimization is usually the last reason for a specific solution, I don't think parsing HJSON should prove much more costly, if at all, than parsing JSON.

json structures are easily described using TypeScript, which is what we write 99% of the tool in. It is "natural" to use json in TypeScript.

So are hjson structures.

Code itself already has great json tooling (schema, IntelliSense, formatting). This does not mean we won't improve yaml support, I'm just pointing out we've already got this in place.

I believe the same tooling should work for hjson as well almost out of the box.

Suggesting to support both yaml and json is pragmatic but also means two code paths (bugs, bloat) and two sets of docs to maintain long term, something we would like to avoid.

I'm not suggesting that. Just support hjson (which is a superset of json).

FYI @chrisdias

Thanks for tagging @chrisdias . Could we reopen this issue until he responds?

@ripper234 thanks for the suggestion!
We discussed and have decided to stay with JSON, despite the limitations. Many of the same reasons apply as in #4851. Of utmost importance is parsing speed because we read a lot of json on startup, and the runtime has a native json parser built in - no dependencies, no module loading.  Another point that was brought up in the discussion was that if anyone wants to interop with us then they have to adopt HJSON which is a speed bump we don't want to introduce.
We recognize that the readability and editing of JSON can be challenging at times, but as you can see with the work we've been doing with settings, we're trying to improve the user experience while keeping the underlying format.
Thanks again for the suggestion, it drove a good debate, please keep them coming.

Thanks for the thorough discussion & answer 👍

authors: chrisdias ripper234 roblourens


text:
one tiny change - "Go To Definition in on Side"

in a code screen, the right click on a method / function gives the user the "Go To Definition". It would be super productive if below that was "Go To Definition in on Side", so that i can control if it opens on the side.

Dupe of #2660?

Yes :+1:

In addition to this action, with the next release you can also Ctrl/Cmd+Alt+Click to get this behavior.

source: gharchive/issue

authors: bpasero joeblew99 mattvperry

repo: Microsoft/vscode

license: MIT

license_type: permissive

license_source: github-api


text:
[Feature Suggestion] Navigate to Folder when entering Folder Name using Keyboard

In explorer of sidebar, I tried to navigate to folder entering folder name.
But there is no such feature in vscode yet.
It would be good if user could use keyboard in explorer.

This issue has already been reported. Please use the search function next time before reporting an issue and/or this time if you are curious about the progress of the issue.

authors: bpasero softdev-zeus


text:
"Screen reader detected" in the status bar should not be clickable

Related to #27479

Open any file in VS Code in Windows
Start Narrator and use it on VS Code
"Screen reader detected" is shown in status bar
Hover on this message. Cursor changes to "hand", but on clicking nothing happens

While this seems to work running out of sources, this does not work in a build:

waaaaaaaaaat... Nice catch!

authors: alexandrudima bpasero ramya-rao-a


text:
Wrong text type recognition behind specific regexp in powershell function

VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:21:47.485Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author
Version

githistory
donjayamanne
0.2.0

code-runner
formulahendry
0.6.24

format-php
Kasik96
1.1.2

perl-debug
mortenhenriksen
0.2.3

PowerShell
ms-vscode
1.4.1

easy-snippet-maker
tariky
0.0.5

plsql-language
xyz
1.0.4

Steps to Reproduce:

type this to VS Code editor as powershell function and see wrong coloring
function aaa {
    param(
        [Parameter()]
        [ValidateScript( {$_ -match '^[_a-z0-9-]+(\.[_a-z0-9-]+)*@[a-z0-9-]+(\.[a-z0-9-]+)*(\.[a-z]{2,4})$'})]
        [string] $ReplyTo = "admins@fi.muni.cz", # everything after end of previous line is brown, but it shouldnt be
        [string] $hascolorasitistext
    )
}

everything after match is brown, as it is common text
but if i use this shorter regexp everything is back to normal

function aaa {
    param(
        [Parameter()]
        [ValidateScript( {$_ -match '^[_a-z0-9-]+(\.[_a-z0-9-]+)*@[a-z0-9-'})]
        [string] $ReplyTo = "admins@fi.muni.cz",
        [string] $hascolorasitistext
    )
}

duplicate of https://github.com/Microsoft/vscode/issues/36991

authors: aeschli ztrhgf


text:
add to .git ignore doesn't add new line

Steps to Reproduce:

open a workspace with a .gitignore or add a .gitignore to the workspace
make sure there is no blank line at the end of the file. mine looks like this:

make a change to a file, open the SCC viewlet, right click on a file and use the command "Add File to .gitignore"

Result: .gitingore file is opened, but the file you added is appended to the last line in the file, not on a new line.

@joaomoreno, @bpasero  I think https://github.com/Microsoft/vscode/pull/30164 will fix this issue. Please take a look.

I would not make this a candidate @kieferrm, doesn't seem that critical.

authors: BugraC chrisdias joaomoreno


text:
Microsoft Visual Code - Suggestion

Hello sir, really i love this Project its amazing and it 'd be much better if you added a feature which alerts us when our Opened files is edited/opened with any kind of another Editors... and then shows a Dialog with 2 optians to tell us to reload opened file (edited one)'s content or just keep current content as its...

Duplicate of #14298

authors: JohnMagdy mjbvz


text:
Minimap noise artifact after resume from suspend on Linux with NVIDIA GPU.

VSCode Version:
Version 1.15.0-insider
Commit f21c311e8db9eff11a605b517525aa6c4dd0f09b
Date 2017-07-25T05:10:14.622Z
Shell 1.6.6
Renderer 56.0.2924.87
Node 7.4.0
Architecture x64
OS Version:
Ubuntu 17.04 (Zesty) w/ Kubuntu backported Plasma Desktop 15.10.4 (Should be irrelevant, but noted just in case.)
NVIDIA Info:
GeForce GTX 750
Driver Version 381.22

Steps to Reproduce:

Have document open in vscode.
Suspend machine to RAM.
Resume from suspend

Reproduces without extensions: Yes
Extra Notes:
KWin had this problem with several applications, too, but they fixed it here: https://bugs.kde.org/show_bug.cgi?id=344326
Perhaps you can reference their fix when addressing this.

@Panoplos Thank you for the report.
May I kindly ask if this issue reproduces in Chromium when opening the following webpage where the same minimap implementation surfaces: https://microsoft.github.io/monaco-editor/
If that is the case, could you please open an issue against Chromium at https://bugs.chromium.org/p/chromium/issues/list and link to it here. I believe it is their responsibility to manage that pixel surface.

Similar: #30292

authors: Panoplos alexandrudima


text:
does the TreeDataProvider API only support typescript ?

I rigistered a provider,and create a TreeDataProvider class with javascript .but it not work

@zsmj1994 Not sure what is not working. Please let us know what is working with some examples or code snippets.


text:
Path must be a string. Received { Error: Command failed: wmic.exe process where parentProcessId=6220 get ExecutablePath,ProcessId

Issue Id: b5402855-71b7-e67e-d7de-652e8588ad90Versions - 1.15.0Stack TypeError: Path must be a string. Received { Error: Command failed: wmic.exe process where parentProcessId=6220 get ExecutablePath,ProcessIdERROR:
Description = The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
    at ChildProcess.exithandler (child_process.js:223:12)    at emitTwo (events.js:106:13)    at ChildProcess.emit (events.js:191:7)    at maybeClose (internal/child_process.js:885:16)     at Process.__dirname.ChildProcess._handle.onexit (internal/child_process.js:226:5)   killed: false,  code: 2147943458,  signal: null,  cmd: 'wmic.exe process where parentProcessId=6220 get ExecutablePath,ProcessId' }    at assertPath (path.js:7:11)    at Object.basename (path.js:799:5)/vs/workbench/parts/terminal/electron-browser/terminalInstance.ts#L894:16 (basename)/vs/workbench/parts/terminal/electron-browser/windowsShellHelper.ts#L49:28 (setTitle)/vs/base/common/winjs.base.raw.js#L1170:0 (onComplete)/vs/base/common/stopwatch.ts#L5:0

Related to #32556.

Duplicate of https://github.com/Microsoft/vscode/issues/32556

authors: Tyriar kieferrm vscodeerrors


text:
Support autoGuessEncoding in ripgrep-based search

Tracking autoGuessEncoding support for search. Currently ripgrep requires you to specify which encoding to search for.
Original encoding discussion is in https://github.com/BurntSushi/ripgrep/issues/1. I don't believe there's a current plan to implement this in Ripgrep.

Ripgrep does support some sort of encoding detection - evaluate whether it's enough for us to add to the extension API and hook up

Not really clear what the effect of --encoding auto in rg is


text:
Add context information when making signature help requests

This is the other half of https://github.com/Microsoft/vscode/issues/752

Is there any timeline on this? We could use this to fix some bugs in the Haxe extension / language server.

Duplicate of #54972

authors: Gama11 jrieken mjbvz


text:
Multiple select in the explorer list (feature request)

VSCode Version: 1.17.0-ins
OS Version: win7x64

If the user has many of unnecessary files, like a.js, b.js, c.js, etc:

It would be great to make a multiple selection by holding Shift , and delete them, or do whatever you want.
Don't you think?

This issue has already been reported. Please use the search function next time before reporting an issue and/or this time if you are curious about the progress of the issue.


text:
Pasting leads to crash

VSCode Version: Code - Insiders 1.18.0-insider (15449873f130d7f3e5604a1cac94f32a1f15f604, 2017-11-02T06:22:24.153Z)
OS Version: Linux x64 4.13.0-16-lowlatency
Extensions: none

Steps to Reproduce:

opened a file
Pasted text from gedit.

This doesn't sound right -- do you mind sharing the text you are pasting? What language are you pasting this in?
Also, if you do Help -> Developer Tools, are there any error messages over there?

authors: octref readonemohamed


text:
Cannot use undefined as a parameter for vscode.debug.startDebugging

VSCode Version: 1.17.2
OS Version: Ubuntu 16.04.3 LTS

Steps to Reproduce:

I am trying to call vscode.debug.startDebugging(undefined, myConfig), but I got the following error if I use undefined as the first parameter.

and my debugger session is terminated afterwards.
Notes:

If I call it with

vscode.debug.startDebugging(vscode.workspace.workspaceFolders[0], myConfig)

then everything works as expected, I could see a debug session launched.

I have put all the attributes defined in the "configurationAttributes" of package.json to the myConfig object (the 2nd parameter), and I declared none of those attributes as required in package.json.

If I just launch  a debug configuration using my debugger type from launch.json, everything works as expected.

I tried to debug vscode code, the call to vscode.debug.startDebugging() can actually return successfully. And I do not see any exception thrown from the call. The Cannot read property uri of undefined error seem to be triggered from a later routine.

By vscode.d.ts#L6105 , I should be able to use undefined as the first parameter.

Reproduces without extensions: Unknown. No opportunity to check, because I am developing a extension.

@changsi-an If you pass undefined for the folder parameter to vscode.debug.startDebugging, the debug configuration myConfig must not contain any variables (like ${workspaceFolder}) because variables are resolved against the folder parameter (which is undefined in your case).
@isidorn we should fail more gracefully in this case, e.g. by not substituting any variables at all.

@weinand I don't have any variables in my myConfig object. All plain strings.

@isidorn most likely passing undefined to startDebugging results in the error from above in https://github.com/Microsoft/vscode/blob/1d632ec12cd4ec0fe4f8badfbb743d5bd2807cda/src/vs/workbench/parts/debug/electron-browser/debugService.ts#L905
because the "root" passed to "doCreateProcess" is "undefined".

@changsi-an good catch, thanks. You can try it out in vscode insiders in 4 days and let us know how ti works.
@weinand thanks for pointing out the issue

vscode.debug.startDebugging(undefined, 'Launch Program'); => nothing happens
vscode.debug.startDebugging(vscode.workspace.workspaceFolders[0], 'Launch Program'); => starts debugging

And I get this error in devtools: Configuration 'Launch Program' is missing in 'launch.json'.

@roblourens
What you are seeing is the expected behaviour.
if you pass undefined for the workspace folder, then no 'launch.json' and consequently no named launch config can be found. However, in this case it is perfectly fine to pass an launch config object to startDebugging.
I agree, the error message Configuration 'Launch Program' is missing in 'launch.json'is misleading because the real problem is that there is no 'launch.json' in the first place.
@isidorn can we make this clearer?

@weinand sure, I have improved the error message to be more precise in hte case the launch.json does not exist.

Oh, I get it.

Is the bug fix released yet? I am still hitting "uri" of undefined error in 1.18.1

No, it's in Insiders or the next stable release.

authors: changsi-an isidorn roblourens weinand


text:
Find in files no longer selects the selection

VSCode Version: Code - Insiders 1.18.0-insider (098bb776d2e5fdf3cc9ea27a233754acf4309857, 2017-11-04T04:35:35.044Z)
OS Version: Darwin x64 16.7.0
Extensions:

Extension
Author (truncated)
Version

EditorConfig
Edi
0.11.1

vscode-terminal-here
Tyr
0.0.5

vscode-svgviewer
css
1.4.3

tslint
eg2
1.0.14

git-project-manager
fel
1.4.0

debugger-for-chrome
msj
3.5.0

seti-icons
qin
0.1.3

gitblame
wad
2.2.0

(4 theme extensions excluded)

Steps to reproduce:

Highlight some work in editor
cmd+shift+f
Notice the word does is no selected in the viewlet

This is really annoying personally as I have muscle memory that I can't shake where I copy, find in files and paste.

It says you have the latest build but this sounds like https://github.com/Microsoft/vscode/commit/ff6c4849cf1b1766a56656e295c86bef71bac685, and all cases work for me now. Please show me tomorrow

The selected text in the editor needs to be different to the text in the viewlet, seems to work fine when the text is the same. Will show you later today 😃

Oh I do see the issue. Easy fix. But if you have selected text in the editor, then it should already copy that text to the search viewlet, so you don't need to paste, right?

authors: Tyriar roblourens


text:
Emmet: Make possible to add spacing before self-closing tag (e.g. in JSX) when using Emmet: Split/Join Tag

It would be handy if there was an option for expanding Emmet tag abbreviation with spacing before closing (/>) bracket in self-closing tag. Right now it expands without spacing, which violates practices in some JS styleguides (e.g. Airbnb's one), and we have to manually add spacing.

VSCode Version: 1.20.1
OS Version: Ubuntu 17.10

Add the below to your settings
"emmet.syntaxProfiles": {
    "jsx": {
        "self_closing_tag": "xhtml"
    }
}

For more on this, see https://docs.emmet.io/customization/syntax-profiles/

@ramya-rao-a Still not working while other syntaxProfiles options are working. Tested with following config (tag_case was added for checking if other options were working) :
    "emmet.syntaxProfiles": {
      "jsx": {
        "self_closing_tag": "xhtml",
        "tag_case": "upper"
      }
    }

I was under the assumption that you were looking for the extra space for the self closing html tags only. But it looks like you want this for custom tags as well when using the Emmet: Split/Join Tag which doesn't respect the syntaxProfiles setting

Sorry, I wasn't clear enough. Yeah, such option will be handy for JSX for aforementioned reasons (e.g. linting validation).

I wonder if there's a problem with adding the space before the /> every time.
I'm not familiar with best practices in HTML, but from what I found online, browsers don't really care if there is a space or not.
@ramya-rao-a any thoughts?

@gushuro We shouldnt add the space everytime. Browsers may not care about the space, this is more to suit coding standards

@gushuro It's all about coding practices, as I mentioned above.

authors: evenfrost gushuro ramya-rao-a


text:
Json formatting can cause selection

Issue Type: Bug
Steps to reproduce

For the json:

[
    {},{
    }
]

Postion cusrsor between the {},{, at the |:

[
    {},|{
    }
]

Run format

Bug
A new selection is created

VS Code version: Code - Insiders 1.21.0-insider (9a04587cc6b42c332609a08bfd7e2dbeac592c21, 2018-03-01T06:39:57.509Z)
OS version: Darwin x64 17.4.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)

Load (avg)
2, 2, 3

Memory (System)
16.00GB (0.05GB free)

Process Argv
/Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron

Screen Reader
no

VM
22%

Extensions (24)

Extension
Author (truncated)
Version

vscode-docker
Pet
0.0.25

color-info
bie
0.5.0

emojisense
bie
0.4.0

lit-html
bie
1.2.0

markdown-checkbox
bie
0.1.1

markdown-emoji
bie
0.0.7

markdown-mermaid
bie
0.1.1

markdown-preview-github-styles
bie
0.1.0

vscode-svgviewer
css
1.4.3

tslint
eg2
1.0.28

vscode-ts-tslintaa
eg2
0.0.1

rest-client
hum
0.17.0

vscode-styled-components
jpo
0.0.16

graphql-for-vscode
kum
1.9.0

mssql
ms-
1.3.0

python
ms-
2018.1.0

azure-account
ms-
0.3.1

csharp
ms-
1.14.0

vsliveshare
ms-
0.1.0-preview.251

debugger-for-chrome
msj
4.1.0

angular2-inline
nat
0.0.17

vscode-code-outline
pat
0.0.13

vscode-java-test
vsc
0.3.0

vscode-maven
vsc
0.5.2

(16 theme extensions excluded)

Reproduces only with extensions

The formatter does an insert edit at the cursor location.

authors: aeschli mjbvz


text:
Hide the notifications center icon from the statusbar if there are no notifications

If there are no notifications, a "full" bell icon will still be displayed in the statusbar, it's not even clickable since there are no notifications to see.
As @bpasero said:

space in the status bar is already very limited, so I would not want to bloat that space anymore than needed

This icon, when there are no notifications, is completely unnecessary in my view, shouldn't we show it only when needed?

We think that hiding the icon is not a good UX idea. Instead we will tackle https://www.github.com/Microsoft/vscode/issues/44509

authors: bpasero fabiospampinato


text:
Extension host terminated unexpectedly. Code: 3221225477 Signal: null vscode how to fix

Issue Type: Bug
The problem is the python extensions and the git-lens and git supercharge extensions please have a look at them. When i took those extensions off it is much better now but i need the python especially**
VS Code version: Code 1.21.1 (79b44aa704ce542d8ca4a3cc44cfca566e7720f1, 2018-03-14T14:46:47.128Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz (4 x 1696)

Memory (System)
5.94GB (2.02GB free)

Process Argv
C:\Program Files\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (22)

Extension
Author (truncated)
Version

html-snippets
abu
0.2.1

path-intellisense
chr
1.4.2

vscode-babel-coloring
dza
0.0.4

EditorConfig
Edi
0.12.1

php-debug
fel
1.12.2

php-intellisense
fel
2.3.0

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.0.15

code-runner
for
0.9.3

beautify
Hoo
1.3.0

phpcs
ika
1.0.5

MagicPython
mag
1.0.12

dotenv
mik
1.0.1

vscode-todo-parser
min
1.9.1

vscode-apache
mrm
1.1.1

debugger-for-chrome
msj
4.2.1

vetur
oct
0.11.7

vscode-icons
rob
7.22.0

code-settings-sync
Sha
2.9.0

guides
spy
0.9.1

code-spell-checker
str
1.6.5

html-css-class-completion
Zig
1.17.1

(1 theme extensions excluded)

Reproduces only with extensions

You should report to the problem extensions, the extension authors should fix the issues.
https://github.com/Microsoft/vscode-python
https://github.com/eamodio/vscode-gitlens

authors: Tyriar ebotchway


text:
ResolveCompletionItem is called on each keystroke

Steps to Reproduce:

Set   "typescript.tsserver.trace": "messages"
In a js file:

function fooooooooooooo() { }

foo

Trigger suggestions at end of foo and start typing

Bug
In the typescript output panel, notice multiple completionEntryDetails calls in the logs as you type. This is caused by vs code calling resolveCompletionItem on the same item again for each keystroke

This has been happening for over a year.

Every letter typed filters the completion list and so the list control is re-filled
When doing so, the variable tracking the current focused item is reset here
Due to this, the code to smartly skip re-rendering the focused item is never reached.
https://github.com/Microsoft/vscode/blob/622eab8bebbe5a7b228cf890fc3ca1665a49bcf1/src/vs/editor/contrib/suggest/suggestWidget.ts#L581-L583

The root cause, is that the variable tracking the current focused item is reset. This was done in https://github.com/Microsoft/vscode/commit/a35c7da7b8f324c1e8cc7830173418e392542f6d. @joaomoreno Do you recall the reason for this change?

My commit message and related issue #23408 seem to be very helpful. I can't even imagine how broken it was 🐛
Serious now: I'm not sure. The suggest widget used to narrow down suggestions by itself, without asking the provider to narrow down, except if the provider returns an incomplete result. I can only reason that in that case, showSuggestions would only be called on the initial population of results; while further "narrow downs" wouldn't pass through that code pass. It seems that even narrowing down now uses showSuggestions, so that assumption is misleading.

Don't reset the item when it's the same completion model?

That works. Pushing this to May as there is no visible user impact of this issue.

Don't reset the item when it's the same completion model?

The completion model differs for each keystroke if there is a completion provider giving result of the incomplete kind. So checking the completion model doesn't always work
Pushed another fix https://github.com/Microsoft/vscode/commit/2e0a56423031aa7b4a8779ea23465128e6ddfef8 which doesn't rely on the completion model.
Moving this bug for June for another round of verification.

authors: joaomoreno jrieken mjbvz ramya-rao-a


text:
Changes in ç letter on the US-Intl keyboard

Something is strange, before version 1.24.0 the letter cedilla was being generated when pressed the symbol ' followed by the letter c.
Now if i do this, the VS Code shows "ć". In this version, i need to press Alt + '.
All my workspace (Gnome) works correctly, only in VS Code i have this issue.
It seems that in the past, Fedora had some problem like this:: https://ask.fedoraproject.org/en/question/28468/problems-with-letter-c-in-us-international-keyboard-fedora-19/

VSCode Version: 1.24.0 - 6a6e02cef0f2122ee1469765b704faf5d0e0d859
OS Version: Ubuntu 18.04 - x64
Keyboard: US-Intl with dead keys.

Steps to Reproduce:

Press the key ' followed by the letter c.
If the letter ç is shown then it is correct, otherwise it is wrong.

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

Did you try Alt + + + C?

@gusbemacbe  Alt+C does nothing, but Alt-right+C give ©.

You forgot of +.
I mean Alt + Plus + C:

@alexandrudima maybe it is not VSCode's problem, but Ubuntu US International keyboard's problem. A Romanian guy suggested to press AltGr + Plus + C to insert cedilla. Click to go #163 on the official issue of Ubuntu at Launchpad:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/518056/comments/163

@gusbemacbe the AltGR+++C also does not work. About the #163 I do not think that's the problem either.
All my workspace is working properly, only happens in VS Code. And only after this last update. I tried doing a downgrade, but it also did not work.
What defines the keyboard layout for the VS Code?

Strange, Luciano, it always works for me on VSCode. I am a multilingual Brazilian and own a Russo-British Apple keyboard and I use the layout English UK Machinotsh International (without dead keys) and always use AltGr + + + C to insert cedilla on VSCode.
Try the layout US International without dead keys and test the same buttons I suggested.

@la-costa It is possible that you have a keybinding bound to ctrl+alt+= that steals the keybinding from typing. You can press ctrl+k ctrl+s and searching for ctrl+alt+ and take a screenshot of that list / unbind ctrl+alt+ keybindings.

Wait, are you speaking of Ctrl or C?

@gusbemacbe i am speaking of C. I am Brazilian, so cedilla (ç) is an important letter for me. Are you using Windows or Linux? Because i think the problem could be only in Linux.
I tried the layout US International without dead keys and also did not work.
An important point is that all my applications work as expected, it's just the VS Code that does not. So I think it's interpreting the wrong layout of the environment. Is there any variable or parameter in the VS Code to set manually?
@alexandrudima I think this is not the cause, but I'm sending what you asked for.

@gusbemacbe i am speaking of C. I am Brazilian, so cedilla (ç) is an important letter for me. Are you using Windows or Linux? Because i think the problem could be only in Linux.

No, I also use the same version of Ubuntu that you are using. I assure you that AltGr + + + C works for me on VSCode Insiders on Ubuntu 18.04 64bits, using UK International (without dead keys) keyboard. Remember that on Linux, UK International, Apple UK International, Apple US International and US International keyboards are same in case of cedilla.
According to the the UK and US International keyboards layouts on Linux:
AltGr + ' or ' + C are designed exclusively for Slavic languages, like Croatian, Czech, Polish and Serbian. Observe that AltGr + ' or ' + any letter also apply for the vocals and some consoants in some Slavic languages, like É, Í, Ó, Ú, Ń, Ź, etc.
AltGr + + are designed for French (C), Portuguese (C), Romanian (S and T) and Turkish (S).

@gusbemacbe ok, I get it, but it does not work.
This is my keyboard layout on the Ubuntu:

Observe the screenshot take from the article of US International on Wikipedia:

The ' + c to insert cedilla works only on Windows. Not applicable on Linux (X11), so you have to AltGr + +  + C.
Source: https://en.wikipedia.org/wiki/QWERTY#US-International

Ah, I am going to test your layout on my Ubuntu.

@gusbemacbe This post has some information about the issue.
https://askubuntu.com/questions/363115/how-to-type-latin-small-letter-c-with-cedilla
After Ubuntu 16.04 the cedilla letter works fine, without need any configuration. The configuration looks ready for GTK and QT.
AltRight+, = "ç" also works.
It looks like the VS Code is no longer using the "IM_MODULE" setting.

Strange, on VSCode, I have just tested the US International with dead keys, pressing Alt + Comma and was able of inserting cedilla. Maybe were you confounding Alt + Quotation with Alt + Comma?

@gusbemacbe No, i am not confounding, but it's so much detail that even I was in doubt :smile:
I my Ubuntu, both works Quotation and Comma. In VS Code, only Comma.
For me it seems something related to the configuration that VS Code uses.

Very good that you have solved. Maybe the Microsoft developers will reconsider IM_MODULE for making Quotation working on VSCode if a French or Brazilian wants to use an US International with dead keys keyboard.
I prefer Apple UK/US International keyboard, building a ABC Extended for X11/Xorg to replace UK/US [Machintosh] International without dead keys on Linux, because it allows me to type in more than 30 pan-Latin languages, including Esperanto, IPA, Vietnamese, Yoruba and Brazilian Amerindian languages. They work perfectly on VSCode.

In version 1.25.1 (or some update of my Ubuntu) the combination 'c worked again.

authors: alexandrudima gusbemacbe la-costa


text:
Test as file name - tasks.json build with g++ gives errors

VSCode Version:1.24.1
OS Version:windows 10 pro version 1803 osbuild 17134.112

Steps to Reproduce:

Pre-requisites: add MinGW
Add c++ tools extension to vscode
Create a file Test.cpp
#include

int main(){
std::out << "Hello world!";
return 0;
}
add c_cpp_properties.json with path to library
{
"configurations": [
{
"name": "Win32",
"includePath": [
"${workspaceFolder}",
"C:/MinGW/lib/gcc/mingw32/6.3.0/include/c++"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"compilerPath": "C:MinGW/bin/gcc.exe",
"intelliSenseMode": "msvc-x64"
}
],
"version": 4
}
add tasks.json
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "Build Test",
"type": "shell",
"command": "echo Hello; g++ -g Test.cpp",
"group": {
"kind": "build",
"isDefault": true
}
}
]
}

Does this issue occur when all extensions are disabled?: No
Errors to build and never works, complains about path or g++ not found.

@TomSputz thanks for your help here. I will mark as needs more info. I agree that without a reproducible test case there is little we can do.

Hey guys
I'd love to help more - I will send some more info with regards to this to
be reproducible.
kind regards
AP
On Mon, Jun 25, 2018 at 5:20 PM, Dirk Bäumer notifications@github.com
wrote:

@TomSputz https://github.com/TomSputz thanks for your help here. I will
mark as needs more info. I agree that without a reproducible test case
there is little we can do.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/52723#issuecomment-399856039,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmpBzA76l0vSDA6gRg27eE_P0DMR2S2kks5uAI9IgaJpZM4U0v1Q
.

Closing since this has had the needs more info tag for six months.

authors: alexr00 dbaeumer loopholer


text:
Support for multi-line JSDoc tags

My apologies if this is not the correct place for this suggestion, but I couldn't find any better places to suggest it.
Basically, I'd really love it if the JSDoc parser that VS Code uses for JavaScript (not TypeScript) intellisense supported multi-line tags.  I know it's possible, as WebStorm/IntelliJ has supported this feature for years.
For example, if I want to fully document my event handlers when using Polymer, each handler method requires all of these @param tags to parse correctly:
/**
* @param {Object} event
* @param {Object} event.details
* @param {String} event.details.foo
* @param {Number} event.details.bar
*/
_someEventHandler(event) {
    /* snip */
}

I can simplify this a bit by using this instead:
/**
* @param {{details: {foo: String, bar:Number}}} event
*/
_someEventHandler(event) {
    /* snip */
}

But that's not exactly readable, and its readability decreases for every additional property on  Object.details. This would be my ideal solution:
/**
* @param {{
*     details: {
*         foo: String,
*         bar:Number
*     }
* }} event
*/
_someEventHandler(event) {
    /* snip */
}

Or when using @typedef tags, rather than doing this:
/**
* @typedef {Object} myCustomType
* @property {String} foo
* @property {Number} bar
* @property {Boolean} baz
*/

I could just do this instead:
/**
* @typedef {{
*     foo: String,
*     bar: Number,
*     baz: Boolean
* }} myCustomType
*/

Whereas right now all I can do to simplify it is:
/**
* @typedef {{foo: String, bar: Number, baz: Boolean}} myCustomType
*/

Which again, is less readable, and gets more unreadable the more properties you have to document.

Thanks for the detailed report.
I believe this is already being tracked here  https://github.com/Microsoft/TypeScript/issues/16179 and here https://github.com/atom/language-javascript/pull/515

Ah, good to know
On Wed, Jun 27, 2018 at 1:01 PM Matt Bierner notifications@github.com
wrote:

Thanks for the detailed report.
I believe this is already being tracked here Microsoft/TypeScript#16179
https://github.com/Microsoft/TypeScript/issues/16179 and here
atom/language-javascript#515
https://github.com/atom/language-javascript/pull/515
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/53161#issuecomment-400755707,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAvR0W_2QlG5srFQr6NpDICXiQGRqKgaks5uA7pWgaJpZM4U6DH-
.

authors: isochronous mjbvz


text:
Markdown references non existing grammars

In 1.25 we now log the scope of grammars that are referenced but can not be found. It's only of severity info, not a real problem, but we might want to fix some references.

open a markdown file
console shows

log.ts:159  INFO No grammar found for scope source.dosbatch
log.ts:159  INFO No grammar found for scope source.scala
log.ts:159  INFO No grammar found for scope source.dart
log.ts:159  INFO No grammar found for scope source.smarty
log.ts:159  INFO No grammar found for scope text.html.javadoc
log.ts:159  INFO No grammar found for scope source.postscript
log.ts:159  INFO No grammar found for scope source.c++
log.ts:159  INFO No grammar found for scope source.js.jquery
log.ts:159  INFO No grammar found for scope source.sass
log.ts:159  INFO No grammar found for scope source.less
log.ts:159  INFO No grammar found for scope source.stylus
log.ts:159  INFO No grammar found for scope source.applescript
log.ts:159  INFO No grammar found for scope text.html.textile

instead of source.dosbatch we have source.batchfile provided by a built-in extension
instead of source.c++ we have source.cpp
replace source.js.jquery with source.js ?
replace source.sass by source.css.scss?
replace source.less by source.css.less

Not markdown in most cases:

source.sass and source.less are coming from the pug grammar.
source.c++ and source.js.jquery are coming from the ruby grammar.

I'll submit a fix for source.dosbatch to our markdown grammar


text:
Can we introduce move files within the folders of a repository as a refactoring feature.

This already exists for js and ts. See https://code.visualstudio.com/updates/v1_24#_update-import-paths-when-a-file-is-moved-or-renamed

authors: mjbvz qb-tarushg


text:
Support recognizing terminals in the dropdown list.

Displaying the path of a terminal is helpful to recognize terminals quickly.

Duplicate https://github.com/Microsoft/vscode/issues/29816

authors: Tyriar ibufu


text:
VSCode extracted from .tar.gz files doesn't work

VSCode extracted from the compressed .tar.gz file doesn't work on my linux System ( elementary OS)
VSCode v1.27
elementary OS v0.4.1 loki 64 bit

for perspective my OS could run Firefox and telegram apps which were extracted from .tar.gz

Try to open with terminal
$ ./code

@yogeshkotadiya didn't work here's the terminal commands I/O
joseph@joseph-G31M-ES2L:~/Downloads/VSCode-linux-x64$ ./code
./code: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
joseph@joseph-G31M-ES2L:~/Downloads/VSCode-linux-x64$ cd .
joseph@joseph-G31M-ES2L:~/Downloads/VSCode-linux-x64$ cd ..
joseph@joseph-G31M-ES2L:~/Downloads$ ./code
bash: ./code: No such file or directory
joseph@joseph-G31M-ES2L:~/Downloads$

ok looks like libgconf package is missing, install it using this command
sudo apt install libgconf2-4
and try again.

@yogeshkotadiya it worked VSCode now works thanks a lot please update this details on your website docs
https://code.visualstudio.com/docs/setup/linux

authors: YousefSaber yogeshkotadiya


text:
VS Code for PowerShell v2

VSCode Version: 1.1
OS Version: Windows Server 2008 R2

Hi,
Is there a support for PowerShell v2 in VSC? What is my concern to use it to develop scripts for SharePoint 2010.
If not - will it be implemented at some point?
Thanks for answer.

@daviwil can you please answer :)

Hi @urbanator84, we currently don't have plans to support PowerShell v2 in the PowerShell extension for VS Code.  If we receive enough requests for this we may consider it.  I'd recommend filing a request for it over at our GitHub page:
https://github.com/PowerShell/vscode-powershell

authors: daviwil isidorn urbanator84


text:
Add Files include include

Issue Type: Feature Request
Now we can use "files exclude", but some projects have too much files to exclude, can we use "files include" to add the files/folders we need?
VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:13:36.375Z)
OS version: Windows_NT x64 10.0.16299

@Lennon925
Not at this point.  The team will have to track and compare the various feature requests.
I would give a thumbs-up to the original issue from @Jackie-Yang , the number of up votes
drives a lot of the process.

This is not likely to happen. Too complicated to think about how the 'excludes' and the 'includes' interact, for example.

authors: Jackie-Yang cleidigh roblourens


text:
crashing after certain amount of time

VSCode Version: 1.29.1

OS Version: manjaro kde

Installed Extensions:
aaron-bond.better-comments ACharLuk.easy-cpp-projects ajshort.include-autocomplete alefragnani.project-manager alexisvt.flutter-snippets bradlc.vscode-tailwindcss CADENAS.vscode-glsllint circledev.glsl-canvas cpylua.language-postcss darkriszty.markdown-table-prettify Dart-Code.dart-code Dart-Code.flutter eamodio.gitlens esbenp.prettier-vscode formulahendry.docker-explorer formulahendry.terminal gcazaciuc.vscode-flow-ide gencer.html-slim-scss-css-class-completion jeroen-meijer.pubspec-assist jock.svg mhmadhamster.postcss-language mrmlnc.vscode-postcss-sorting mrmlnc.vscode-scss ms-python.python ms-vscode.cpptools ms-vsliveshare.vsliveshare msjsdiag.debugger-for-chrome Nash.awesome-flutter-snippets nickdodd79.gulptasks Orta.vscode-react-native-storybooks PeterJausovec.vscode-docker quicktype.quicktype robertohuertasm.vscode-icons shinnn.stylelint sldobri.daily slevesque.shader twxs.cmake vector-of-bool.cmake-tools

Log:

Does this issue occur when all extensions are disabled?: Not sure... seems like it doesn't.

I guess this doesn't happen if you run code --disable-extension, right?

well... the problem isn't occurring anymore even in normal mode... dunno why or how... I was facing this for last 2 days... pfff... I'll give an update if the problem occurs again... thanks <3

authors: audacioustux octref


text:
Screencast Mode - text not resetting

In screencast mode, text overflows to multiple lines:

Might be better to limit to one line?
@joaomoreno

Hi, I'm going to try working on this one!

authors: flurmbo mkenigs


text:
cmd proble

Issue Type: Feature Request
no cmd open
VS Code version: Code 1.32.1 (05f146c7a8f7f78e80261aa3b2a2e642586f9eb3, 2019-03-08T00:51:49.278Z)
OS version: Windows_NT x64 6.2.9200

Please describe the issue in more detail

authors: arifsanadi roblourens


text:
Reference in not showing proper when C# file has class and Data annotations

Issue Type: Bug
Create any C# Class which have data annotation and where you see the reference link, which is wrapped with Data annotation, you can be able to see it properly.
See the Screenshot for more details.

VS Code version: Code - Insiders 1.34.0-insider (473af338e1bd9ad4d9853933da1cd9d5d9e07dc9, 2019-05-01T00:22:05.899Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 x 3600)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
11.89GB (2.70GB free)

Process Argv
--file-uri file:///d%3A/Projects/NFQ/NFQ.code-workspace

Screen Reader
no

VM
0%

Extensions (35)

Extension
Author (truncated)
Version

ng-template
Ang
0.1.11

vscode-custom-css
be5
3.0.4

htmltagwrap
bra
0.0.7

simple-react-snippets
bur
1.2.2

bracket-pair-colorizer
Coe
1.0.61

vscode-eslint
dba
1.8.2

es7-react-js-snippets
dsz
2.2.1

vscode-great-icons
emm
2.1.47

vsc-material-theme
Equ
2.8.2

file-icons
fil
1.0.17

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.0.15

vscode-google-translate
fun
1.1.5

csharpextensions
jch
1.3.0

Angular2
joh
7.1.4

svn-scm
joh
1.48.1

csharpfixformat
Leo
0.0.81

vscode-language-babel
mgm
0.0.22

python
ms-
2019.4.12954

csharp
ms-
1.19.0

vscode-typescript-tslint-plugin
ms-
1.0.0

debugger-for-chrome
msj
4.11.3

nested-comments
phi
2.3.0

material-icon-theme
PKi
3.7.0

quicktype
qui
12.0.46

csharp2ts
raf
0.0.22

code-settings-sync
Sha
3.2.9

vscode-fileutils
sle
2.13.7

code-spell-checker
str
1.7.6

ayu
tea
0.18.0

highlight-matching-tag
vin
0.9.1

vscodeintellicode
Vis
1.1.5

vscode-icons
vsc
8.6.0

change-case
wma
1.0.0

JavaScriptSnippets
xab
1.7.2

(15 theme extensions excluded)

/duplicate https://github.com/Microsoft/vscode/issues/71745

authors: Tyriar kevindrc


text:
use .gitignore to ignore search inside files and folders

use .gitignore to know which files and folders not to search into (think node_modules or packages)

I don't think .gitignore should dictate this, in other text editors it's normally done on a project setting or editor setting-level.

atom does this. there's no need for project settings or editor settings. If I'm git-ignoring it, there's no need to make this searchable or "autocompletable" (I just invented that word)

Huh it does too, I guess I'm thinking of sublime.

This is a feature request, not a bug report/issue. Feature suggestions already have a place over at vscodes uservoice.

Ops! Sorry. I didn't know there was a uservoice.

@luisrudge reopening. We haven't fully figured out what to discuss on user voice and what to discuss in a feature request issue.
This feature request is better discussed here. In particular since the last comment in user voice is not correct :disappointed: .
I could imagine a meta property 'USE_GITIGNORE' and that would be a great opportunity for a pull request:
	"files.exclude": {
		"USE_GITIGNORE": true
	},

@bpasero fyi.

+1

I'm not sure I like the idea of having this as a opt-in flag.. This really should be the default behavior, since searching inside node_modules is not a good thing and certainly isn't the most common use case. Maybe we can add a flag to opt-out this behavior?
Also, I'd like to do this! Can you help me understand which parts of vscode would have to change? THanks!

I think in the example above it should really be search.exlude and not files.exclude because the former will exclude it from search but the latter from everywhere in the UI including the explorer.
We are reading this setting in from https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/search/common/searchQuery.ts#L18 and I think we could add code there to check for another setting that - if enabled - would mix in anything from .gitignore.

as @luisrudge already said, this should be the default behaviour like in atom and sublime.

@bpasero so.. just add code to read from .gitignore and push that files/folders to searchExcludes ?

@luisrudge well we also have to convert it to the glob pattern format we use in VS Code. If you look at the default settings and how we ignore the .git folder there you can get an idea of the syntax.

I agree with @luisrudge that this should be the default behavior, but perhaps there is an intermediate solution we can go for first:
Results from tracked files should come first. Results from git-ignored files should come last.
This is a lower-risk change that, IMO, can be implemented immediately and yield a notable user experience benefit for search.
Currently, results from git-ignored files are mixed in with results from tracked files. This is super noisy, for example, if you're developing in Python and have a virtual environment or build folder within your project folder with all kinds of code that matches almost anything you might search for.
If you're searching for a string across your project, I wager in 100% of cases you want results from your tracked files first, perhaps followed by results from untracked but not ignored files.
Would it make sense to implement this behavior first? Basically, just tweaking the order in which in the results are displayed. I don't think we would even need a new setting for that.

I think the behavior I described should also apply to the behavior of Command + P, when you want to switch to a file and there are multiple possible matches for the user's search term.

Currently the sorting is based on our scoring algorithm. I do not think it would make sense to change the sorting based on other criteria unless there is a good way to explain this to the user.

the sorting can stay the same, just ignore the files listed in .gitignore. this is the absolute main thing that keeps me from using code.

@bpasero - Could you elaborate? I think the change I'm describing is very easy to explain.
Here's take 2 at explaining the change, simplifying what I said earlier:
Search results are divided into 2 sections--tracked files and everything else. Tracked files always show up first. Results within each section are sorted according to the current scoring algorithm.
In addition to being easy to explain, this is the behavior I wager most people would expect.
As I commented earlier, Python projects generally have venv, dist, and build subfolders which contain many Python files, some of which are even copies of the main project files from the last packaging build. These are not part of the project and you don't check these files in because they are copied from third-parties or auto-generated.
Treating these files as equal to the main project files severely detracts from the usability of search. No one wants to see results from these files at the top, if even at all.
I'm sure other languages have similar problems as well.
If ignoring these files in search results is too big of a step to take, then I think the tweak I'm describing here yields the same usability benefit while being straightforward to explain.

@nchammas I do think that the right fix is to just exclude those files when .gitignore is present and the setting to respect it. otherwise one could also argue why we are not doing the same sorting trick for the search/files exclude setting.
The real work here is to translate .gitignore patterns into our ignore patterns and making sure the solution scales. I have seen .gitignore files with 1000+ rules that would need to be applied many times over many paths.

Adding my :+1:. This would solve one of the issues I encountered in the ember-cli test tour, saving devs from setting up a vscode-specific config file. Related PR: https://github.com/ember-cli/ember-cli/pull/5643

Would be nice to not show git ignored files in the project explorer :)

@bpasero tried fixing this as this https://github.com/asotog/vscode/commit/d3cac5b26e57521dc39f8390e3cdf76c1f917342

I think Atom behavior is a reasonable default configuration. .gitignored files and directories are still accessible from the sidebar explorer, but greyed out in the UI and not searched in with project-level search.
About parsing, there are libraries like https://www.npmjs.com/package/gitignore-parser but I don’t know if their implementation is completely correct.

I would like to start working on it.
I'll read through the relevant code and try sending a PR within a week or two.

+1

I think this I'll leave this one to someone more capable than me. The size of the project is kind of overwhelming for me and this doesn't look like a monkey-patching issue.

Estimates on completion of this? It's the only thing I still need atom installed on my PC for.

is someone working on this ? i would like to help on this one :P @bpasero

It is not being worked on currently. My main concern is how to make a large .gitignore list performant enough against our glob exclude matching.

@bpasero can you define large? Here are some common examples https://github.com/github/gitignore

@Tyriar yup (https://chromium.googlesource.com/chromium/src.git/+/master/.gitignore):
*.gypcmd
*.mk
*.ncb
*.opensdf
*.orig
*.pdb
*.props
*.pyc
*.pyproj
*.rules
*.sdf
*.sln
*.sublime-project
*.sublime-workspace
*.suo
*.targets
*.user
*.vc.opendb
*.vcproj
*.vcxproj
*.vcxproj.filters
*.vpj
*.vpw
*.vpwhistu
*.vtg
*.xcodeproj
*.xcworkspace
*.VC.db
*_proto.xml
*_proto_cpp.xml
*~
!Android.mk
.*.sw?
.DS_Store
.classpath
.cproject
.gdb_history
.gdbinit
.landmines
.metadata
.project
.pydevproject
.checkstyle
cscope.*
GPATH
GRTAGS
GSYMS
GTAGS
Session.vim
tags
Thumbs.db
v8.log
vs-chromium-project.txt
# Settings directories for eclipse
/.externalToolBuilders/
/.settings/
/.vs/
# Visual Studio Code
/.vscode/
/_out
/android_emulator_sdk
/ash/ash_unittests_run.xml
/base/base_unittests_run.xml
/breakpad/src/
/build/android/bin
/build/Debug
/build/Debug_x64
/build/goma
/build/gomacc.lock
/build/ipch/
/build/Release
/build/Release_x64
/build/win_toolchain.json
/build/util/LASTCHANGE*
/build/util/support
/build/x64/
/build/linux/bin/eu-strip
/build/linux/debian_*-sysroot/
/build/linux/ubuntu_*-sysroot/
/build/mac_files
/buildtools
# The Chrome OS build creates a /c symlink due to http://crbug.com/54866.
/c
/cdm
/ceee/internal/
/chrome/angle_unittests_run.xml
/chrome/content_gl_tests_run.xml
/chrome/gl_tests_run.xml
/chrome/gles2_conform_test_run.xml
/chrome/tab_capture_performance_tests_run.xml
/chrome/telemetry_gpu_test_run.xml
/chrome/app/theme/default_100_percent/google_chrome
/chrome/app/theme/default_200_percent/google_chrome
/chrome/app/theme/google_chrome
/chrome/browser/autofill/internal
/chrome/browser/chromeos/login/screenshot_testing/golden_screenshots/*.png
/chrome/browser/chromeos/login/screenshot_testing/artifacts
/chrome/browser/extensions/api/ledger/
/chrome/browser/extensions/default_extensions/chromeos
/chrome/browser/google/linkdoctor_internal
/chrome/browser/internal
/chrome/browser/performance_monitor/performance_monitor.xml
/chrome/browser/protector/internal
/chrome/browser/resources/chromeos/quickoffice
/chrome/browser/resources/pdf/html_office
/chrome/browser/resources/media_router_internal/
/chrome/browser/resources/settings_internal/
/chrome/browser/resources/software_rendering_list
/chrome/browser/spellchecker/internal
/chrome/browser_tests_run.xml
/chrome/chrome_run.xml
/chrome/chrome_user32_delay_imports.xml
/chrome/chrome_version_resources.xml
/chrome/common/extensions/api/api.xml
/chrome/common/extensions/api/ledger/
/chrome/Hammer
/chrome/installer/linux/internal
/chrome/installer/mac/internal
/chrome/installer/mac/third_party/xz/xz
/chrome/installer/mini_installer.xml
/chrome/installer/mini_installer/mini_installer.aps
/chrome/installer/mini_installer/support
/chrome/installer/mini_installer_syzygy.xml
/chrome/installer/mini_installer_tests_run.xml
/chrome/installer_util_strings.xml
/chrome/interactive_ui_tests_run.xml
/chrome/setup.xml
/chrome/setup_unittests.xml
/chrome/supplement.gypi
/chrome/sync_integration_tests_run.xml
/chrome/test/android/telemetry_tests/browser_tests/*.wpr
/chrome/test/chromeos/autotest/files/client/deps/chrome_test/test_src/
/chrome/test/chromeos/autotest/files/client/deps/page_cycler_dep/test_src/
/chrome/test/chromeos/autotest/files/client/deps/perf_data_dep/test_src/
/chrome/test/chromeos/autotest/files/client/deps/pyauto_dep/test_src/
/chrome/test/chromeos/autotest/files/client/deps/telemetry_dep/test_src/
/chrome/test/data/extensions/api_test/permissions/nacl_enabled/bin
/chrome/test/data/firefox2_profile/searchplugins
/chrome/test/data/firefox2_searchplugins
/chrome/test/data/firefox3_profile/searchplugins
/chrome/test/data/firefox3_searchplugins
/chrome/test/data/gpu/vectortown_endurance/
/chrome/test/data/gpu/vt/
/chrome/test/data/layout_tests
/chrome/test/data/osdd
/chrome/test/data/pdf_private
/chrome/test/data/perf/canvas_bench
/chrome/test/data/perf/frame_rate/content
/chrome/test/data/perf/frame_rate/private
/chrome/test/data/perf/private/
/chrome/test/data/perf/third_party/
/chrome/test/data/plugin/
/chrome/test/data/webrtc/resources
/chrome/test/media_router/internal
/chrome/tools/memory
/chrome/tools/test/reference_build
/chrome/unit_tests_run.xml
/chrome/web_ui_mojo_bindings.xml
/chrome_elf/chrome_elf_resources.xml
/chromecast/internal
/clank
/cloud_print/cloud_print_version_resources.xml
/components/chrome_settings_proto_generated_compile.xml
/components/cloud_policy_proto_generated_compile.xml
/components/gcm_driver.xml
/components/leveldb_proto_test_support.xml
/components/rappor.xml
/components/resources/default_100_percent/google_chrome
/components/resources/default_200_percent/google_chrome
/components/search_engines/prepopulated_engines.xml
/components/suggestions.xml
/components/variations.xml
/content/browser/service_worker/proto.xml
/content/content_browsertests_run.xml
/content/content_common_mojo_bindings.xml
/content/content_unittests_run.xml
/content/test/data/gpu/generated/
/content/test/data/gpu/gpu_reference/
/content/test/data/layout_tests/
/content/test/data/plugin/
/content/web_ui_test_mojo_bindings.xml
/data
/delegate_execute
/device/serial/device_serial_mojo.xml
/google_apis/gcm/gcm.xml
/google_apis/internal
/googleurl
/gpu/gles2_conform_test
/infra/.recipe_deps
/internal_gyp
/ios/third_party/earl_grey/src
/ios/third_party/fishhook/src
/ios/third_party/gcdwebserver/src
/ios/third_party/material_text_accessibility_ios/src
/ios/third_party/ochamcrest/src
/ios_internal
/llvm
/media/cast/logging/cast_logging_proto_lib.xml
/media/cdm/api
/media/media_asm.xml
/media/media_mojo_bindings.xml
/media/test/data/internal
/media/yuv_convert_simd_x86.xml
/metro_driver
/mojo/hello_world_service.xml
/mojo/mojo_application_bindings.xml
/mojo/mojo_application_manager_unittests.xml
/mojo/mojo_apps_js_bindings.xml
/mojo/mojo_apps_js_unittests_run.xml
/mojo/mojo_clipboard_bindings.xml
/mojo/mojo_content_handler_bindings.xml
/mojo/mojo_core_window_manager_bindings.xml
/mojo/mojo_echo_service_bindings.xml
/mojo/mojo_example_service_bindings.xml
/mojo/mojo_external_service_bindings.xml
/mojo/mojo_geometry_bindings.xml
/mojo/mojo_gles2_bindings.xml
/mojo/mojo_gpu_bindings.xml
/mojo/mojo_input_events_bindings.xml
/mojo/mojo_js_unittests_run.xml
/mojo/mojo_keyboard_bindings.xml
/mojo/mojo_launcher_bindings.xml
/mojo/mojo_media_viewer_bindings.xml
/mojo/mojo_native_viewport_bindings.xml
/mojo/mojo_navigation_bindings.xml
/mojo/mojo_network_bindings.xml
/mojo/mojo_public_bindings_unittests.xml
/mojo/mojo_public_test_interfaces.xml
/mojo/mojo_public_unittests.xml
/mojo/mojo_sample_service.xml
/mojo/mojo_shell_bindings.xml
/mojo/mojo_shell_lib.xml
/mojo/mojo_spy.xml
/mojo/mojo_surface_id_bindings.xml
/mojo/mojo_surfaces_app_bindings.xml
/mojo/mojo_surfaces_bindings.xml
/mojo/mojo_test_service_bindings.xml
/mojo/mojo_view_manager_bindings.xml
/mojo/mojo_window_manager_bindings.xml
/mojo/mojo_wm_flow_embeddee_bindings.xml
/mojo/mojo_wm_flow_embedder_bindings.xml
/mojo/mojom_test.xml
/mojo/sample_service.xml
/native_client
/net/Debug
/net/net_derived_sources.xml
/net/net_unittests_run.xml
/net/Release
/net/testserver.log
/out*
/ppapi/native_client/nacl_irt.xml
/ppapi/native_client/ppapi_lib.xml
/remoting/android/internal/
/remoting/appengine/
/remoting/host/installer/linux/internal/
/remoting/ios/
/remoting/internal/
/remoting/proto/chromotocol_proto_lib.xml
/remoting/remoting_core_resources.xml
/remoting/remoting_elevated_controller.xml
/remoting/remoting_host.xml
/remoting/remoting_host_event_logger.xml
/remoting/remoting_host_installation.xml
/remoting/remoting_host_messages.xml
/remoting/remoting_infoplist_strings.xml
/remoting/remoting_lib_idl.xml
/remoting/remoting_lib_rc.xml
/remoting/remoting_me2me_host.xml
/remoting/remoting_native_messaging_manifests.xml
/remoting/remoting_version_resources.xml
/remoting/remoting_windows_resources.xml
/remoting/test/internal/
/remoting/tools/internal/
/remoting/webapp/app_remoting/internal/
/sandbox/linux/seccomp-legacy/
/sdch/open-vcdiff
/seccompsandbox
/signing_keys
/skia/tools/clusterfuzz-data/
/sql/sql_unittests_run.xml
/sync/sync.xml
/sync_testserver.log
/testing/gmock
/testing/gtest
/testserver.log
/tools/luci-go/linux64/isolate
/tools/luci-go/mac64/isolate
/tools/luci-go/win64/isolate.exe
/third_party/__START__
/third_party/accessibility-developer-tools/
/third_party/accessibility_test_framework/lib/*.jar
/third_party/adobe/flash/binaries
/third_party/adobe/flash/symbols
/third_party/amd/
/third_party/android_protobuf/src
/third_party/android_support_test_runner/lib/*.aar
/third_party/android_support_test_runner/lib/*.jar
/third_party/android_tools/
/third_party/android_tools_internal/
/third_party/android_webview_glue/src
/third_party/angle
/third_party/angle_dx11
/third_party/apache-mime4j
/third_party/apache-portable-runtime/src
/third_party/apache_velocity/lib/*.jar
/third_party/apache-win32/bin/*.exe
/third_party/apache-win32/bin/*.dll
/third_party/apache-win32/bin/iconv/*.so
/third_party/apache-win32/modules/*.so
/third_party/apache-win32/modules/*.dll
/third_party/asan
/third_party/bidichecker
/third_party/bison
/third_party/boringssl/src
/third_party/bouncycastle/lib/*.jar
/third_party/byte_buddy/lib/*.jar
/third_party/cacheinvalidation/cacheinvalidation_unittests_run.xml
/third_party/cardboard-java/src
/third_party/catapult
/third_party/ced/src
/third_party/chromeos_login_manager
/third_party/chromeos_text_input
/third_party/chromite
/third_party/cld_2/src
/third_party/cld_3/src
/third_party/colorama/src
/third_party/cros
/third_party/cros_system_api
/third_party/custom_tabs_client/src
/third_party/cygwin
/third_party/deqp/src
/third_party/directxsdk
/third_party/dom_distiller_js/dist
/third_party/drmemory/drmemory-windows-sfx.exe
/third_party/drmemory/unpacked
/third_party/elfutils/src
/third_party/errorprone/lib
/third_party/espresso/lib/*.jar
/third_party/eyesfree/src
/third_party/ffmpeg
/third_party/findbugs
/third_party/flac
/third_party/flatbuffers/src
/third_party/fontconfig/src
/third_party/freetype-android/src
/third_party/freetype2/src
/third_party/gles2_conform
/third_party/glslang/src
/third_party/gnu_binutils/
/third_party/google_appengine_cloudstorage
/third_party/google_toolbox_for_mac/src
/third_party/googlemac
/third_party/gvr-android-sdk/src
/third_party/gperf
/third_party/grpc
/third_party/guava/lib/*.jar
/third_party/hamcrest/lib/*.jar
/third_party/httpcomponents-client
/third_party/httpcomponents-core
/third_party/hunspell_dictionaries
/third_party/icu
/third_party/icu4j/lib/*.jar
/third_party/intellij/lib/*.jar
/third_party/jarjar
/third_party/javax_inject/lib/*.jar
/third_party/jsoncpp/source
/third_party/jsr-305/src
/third_party/junit/src
/third_party/kasko
/third_party/khronos_glcts
/third_party/leakcanary/src
/third_party/leveldatabase/src
/third_party/leveldb
/third_party/libc++-static/libc++.a
/third_party/libaddressinput/src
/third_party/libexif/sources
/third_party/libFuzzer/src
/third_party/libjingle/source
/third_party/libjpeg_turbo
/third_party/liblouis/src
/third_party/libphonenumber/dist
/third_party/libsrtp
/third_party/libupnp
/third_party/libvpx/source/libvpx
/third_party/libwebm/source
/third_party/libyuv
/third_party/lighttpd
/third_party/llvm
/third_party/llvm-allocated-type
/third_party/llvm-bootstrap
/third_party/llvm-build
/third_party/lss
/third_party/mesa/src
/third_party/mingw-w64
/third_party/minigbm/src
/third_party/mkl
/third_party/mocha
/third_party/mockito/src
/third_party/nacl_sdk_binaries/
/third_party/netty-tcnative/src
/third_party/netty4/src
/third_party/nss
/third_party/objenesis/lib/*.jar
/third_party/omaha/src/omaha
/third_party/openmax_dl/
/third_party/openh264/src
/third_party/ow2_asm/lib/*.jar
/third_party/pdfsqueeze
/third_party/pdfium
/third_party/pefile
/third_party/perl
/third_party/platformsdk_win7
/third_party/platformsdk_win8
/third_party/ppapi
/third_party/psyco_win32
/third_party/pthreads-win32
/third_party/py_trace_event/src
/third_party/pyelftools
/third_party/pyftpdlib/src
/third_party/pylib
/third_party/pymox/src
/third_party/python_24
/third_party/python_26
/third_party/pywebsocket/src
/third_party/pywebsocket/src
/third_party/re2/src
/third_party/requests/src
/third_party/robolectric/lib/*.jar
/third_party/robolectric/robolectric
/third_party/scons-2.0.1
/third_party/sfntly/src
/third_party/shaderc/src
/third_party/skia
/third_party/smhasher/src
/third_party/snappy/src
/third_party/SPIRV-Tools/src
/third_party/sqlite4java/lib/**/*.dll
/third_party/sqlite4java/lib/**/*.jar
/third_party/sqlite4java/lib/**/*.jnilib
/third_party/sqlite4java/lib/**/*.so
/third_party/swiftshader/
/third_party/syzygy
/third_party/syzygy/binaries
/third_party/tsan/
/third_party/ub-uiautomator/lib
/third_party/usb_ids
/third_party/usrsctp/usrsctplib
/third_party/v8-i18n
/third_party/valgrind
/third_party/v4l2capture
/third_party/visualmetrics
/third_party/wayland/src
/third_party/wayland-protocols/src
/third_party/wds/src
/third_party/webdriver/pylib
/third_party/webdriver/python/selenium
/third_party/webgl
/third_party/webgl/src
/third_party/webpagereplay/
/third_party/webrtc
/third_party/widevine/cdm/chromeos
/third_party/widevine/cdm/linux
/third_party/widevine/cdm/mac
/third_party/widevine/cdm/win
/third_party/widevine/test/license_server
/third_party/win_toolchain/.timestamps
/third_party/win_toolchain/files
/third_party/wix
/third_party/xdg-utils
/third_party/xulrunner-sdk
/third_party/yasm/binaries
/third_party/yasm/generate_files.xml
/third_party/yasm/source/patched-yasm
/third_party/yasm/yasm.xml
/tools/.bisect-builds-cache.json
/tools/distcc
/tools/gn/bin/linux
/tools/gn/bin/mac
/tools/gn/bin/win
/tools/gyp
/tools/histograms
/tools/json_schema_compiler/test/json_schema_compiler_tests.xml
/tools/metrics/actions/actions.old.xml
/tools/metrics/histograms/histograms.before.pretty-print.xml
/tools/page_cycler/acid3
/tools/perf/data
/tools/perf/internal
/tools/perf/results.html
/tools/swarming_client
/tools/tryserver
/tools/win/link_limiter/build
/ui/file_manager/internal
/ui/keyboard/keyboard_mojom_bindings.xml
/ui/surface/surface.xml
/ui/surface/surface_gpu_tests.xml
/v8
/webkit/data
/webpagereplay_logs/
/win8/delegate_execute/delegate_execute_version_resources.xml
/win8/metro_driver/metro_driver_version_resources.xml
/x86-generic_out/
/xcodebuild

@bpasero ag respects .gitignore and claims to be very performant. The only problem is it needs some effort to get it to work on Windows.

ag has broken gitignore support. It doesn't support directory excludes properly. And let's try to keep external dependencies to a minimum.
@bpasero What would happen if all rules from .gitignore were inputted to the exclude glob field found when searching? Apart from speed issues I mean.

I think it would work apart from an unusable slow search :). I think instead of trying to make the gitignore patterns work with our world we should shell out to git itself and ask it if a certain list of paths are valid paths for tracking changes.

/cc @chrmarti

@bpasero I think git has something like that. Mercurial has a command hg status -i which lists the ignored files present in the work tree and a similar command that shows all the tracked files and directories. Something similar can be achieved for git I think.

would it be possible to write an extension to do this?

Currently not.

@bpasero i personally think for search is fine to keep it as it is now, results returns from any file (even ignored).
But for files explorer (tree view) this is helpful, and won't affect performance, even, might increase it because will not be showing useless files (from dev perspective you dont want to see node_modules, bower files, js maps, transpiled js, some times etc) on that view, here is a library that seems doing that https://github.com/atom/git-utils#repositoryisignoredpath  BUT  built by the neighbors :(

I've moved from VS Code to Atom and am now exploring the possibility of moving back to VS Code again, but this is one thing that really makes me want to stick with Atom for the time being.  Having to make sure the results I'm looking through aren't in /tmp or /dist folders manually is a real pain.

I think this should be a switch in the search itself, like "regex", "whole word" and "match case" because I usually want it, but the times I don't want it are not rare, and I want to be able to just turn it off and search without changing configs or anything.
For example, I might have files that have been installed by bower that I want to include in a particular search because I'm trying to figure out how a library works, or maybe I want to include log / debug files that my code has written, but are gitignored.
I think that if I try and search inside a folder, which has itself been completely .gitignored, I am signalling my intent to search it anyway - it would be good if the "ignore .gitignored" button could be greyed out in this case.

Just tried out Visual Studio 2017 RC with the new “Open Folder” feature. They seem to respect .gitignore out of the box. I was kind of pleasantly surprised. No word on performance (performance is not really Studio's thing anyway.)

It seems people are either rooting for having Code respect .gitignore for search results, or file explorer, or both.
I think the option should be set for both, but we should have to possibility to let the file explorer show .gitignored files while not displaying them in search results, or the other way around.

2017 and Still don't ignore repo ignore files? :stuck_out_tongue:

Everytime i want to use vscode for my projects, i face this issue: showing all dot files, cache files, build files, indexed, which are all declared to be ignored in the .gitignore, make the editor unusable:

it pollute the CMD+P search
it pollute the tree
it pollute the search in all files

:(

on every project i have to use the exclude files, via .vscode/settings.json and waster .gitignore functionality :(

I also would propose to not simply hide files but make them transculent in the sidebar so you can still open files and folders which are ignored BUT you can't search them and you see a visual indicator that it's not watched in your project.
Thats the only feature keeping me away from using VS Code on a daily base.

+1 for hiding .gitignore files from the file browser. If it's not the default behavior, at least having the option to hide these files would be ideal. The lack of this feature is keeping me in Atom (and Atom's freeze-ups are driving me nuts).

+1 to implement .gitignore functionality finally

@denieler  where did they implement?

Any new update on this feature? For me it's still the main issue why I don't use vscode over atom.
For me this should handle

Tree view (blending out files which are gitignored)
Quick Open Panel (Remove or move all gitignored files down in the list)
Search (Remove gitignored files from search)

I would like to check if I can find some way to implement it but it will take me a bit to get into the project.

@db2k yeah.. I even wanted to jump from Atom to VS code, but when I found this issue now I'm not sure..

At the moment you can still use files.exclude and search.exclude. Still hope to support gitignore in the future.

@roblourens yeah, but it is kind of lame.. it is 2017 already, not 2004

The problem is that I work on a lot of projects at the same time and setting up files.exclude and search.exclude in addition everytime for every project would be really a pain since I already have all that stuff in my .gitignore for each project.
Since VSCode is such a gitrelated editor with the Git sidebar etc. I guess that should just be an inbuild option to toggle if you need it or not... No way to fetch the project folders gitignore and merge the arrays into the file/search exclude arrays?
I'm not a pro with typescript which is why I can't really help for now since I would have to read me in first, but otherwise I would like to contribute somehow so we can get this feature in.

This bug is super frustrating and actually causes me to lose work on a regular basis. To repro:
npm install -g electron-forge
git clone https://github.com/paulcbetts/trickline && cd trickline

## This creates a folder called 'out', which is ignored in my gitignore. However,
## it will have a copy of every source file in my project, with the same names
electron-forge package

code .

Now use Ctrl/Cmd-T to open a file. Whoops! You now have a 50% chance of editing the file in out, which is at best annoying, causes you to constantly wonder "WHY DIDNT MY CHANGE DO ANYTHING????", and at worst, loses data when out gets deleted by a git clean -xdf along with your accidental changes.
VS Code understands Git in lots of other ways, there's no reason it can't parse gitignore. libgit2 will even do this on your behalf and help you out to do so.

@paulcbetts wow. that's shitty. I never thought of that. Not sure if anyone reads this issue though. Lots of people asking for it, but no one answering..

@paulcbetts In your case, you probably want to exclude out via your tsconfig, since cmd+T is showing you files from the language service. It will also remove duplicates from 'find all references', etc. Since files.exclude doesn't currently impact those features, .gitignore support as I'm imagining it wouldn't either. (And maybe I'm wrong, but I often want to use language service features on gitignored files like node_modules)

@paulcbetts @luisrudge @roblourens  i'm using vscode exclusion, meanwhile this moves forward

In your case, you probably want to exclude out via your tsconfig, since cmd+T is showing you files from the language service
(And maybe I'm wrong, but I often want to use language service features on gitignored files like node_modules)

@roblourens Cmd-T will really show you files in node_modules? I feel like there's got to be an extra layer of exclusion because that would be super noisy if it showed me every file in there

Hey after waiting for someone else to do it, I ended up putting together a small extension that copies your gitignore into your vscode workspace settings with one command: https://github.com/stubailo/vscode-ignore-gitignore
Let me know if this is useful, and looking forward to feedback and PRs! I've only tried it in a few projects but seems to work so far.

@paulcbetts regarding:

Cmd-T will really show you files in node_modules?

Cmd-T shows you all the symbols in your workspace. This includes symbols from node modules (and even local variables).
Regarding:

You now have a 50% chance of editing the file in out

The "out" folder includes the typescript source files in "out\trickline-win32-x64\resources\app\src" and the way the TypeScript language service is configured in the top-level "tsconfig.json" these files are part of the project context. They are therefore analyzed by TypeScript. To address this you should add an exclude of "out" to your "tsconfig.json" as shown below:
{
  "compilerOptions": {
    "removeComments": false,
    "preserveConstEnums": true,
    "declaration": true,
    "experimentalDecorators": true,
    "noImplicitAny": true,
    "noImplicitReturns": true,
    "suppressImplicitAnyIndexErrors": true,
    "strictNullChecks": true,
    "noUnusedLocals": true,
    "noImplicitThis": true,
    "noUnusedParameters": true,
    "module": "commonjs",
    "moduleResolution": "node",
    "pretty": true,
    "target": "es2015",
    "jsx": "react",
    "outDir": ".tmp/build"
  },
  "formatCodeOptions": {
    "indentSize": 2,
    "tabSize": 2
  },
  "types" : [
    "node",
    "electron"
  ],
  "exclude": [
    "out"
  ]
}

@egamma that's the whole point we're trying to get here... If we already have out in our .gitignore file, why would I have to add it to the tsconfig file again?

Exactly, there should actually be more like a hierarchy for that.
.gitignore should always the first ignore configuration to be loaded and should be merged with other vscode specific ignore configs.

@egamma I already have a place where I describe what files my editor should ignore, .gitignore :)

Thanks @stubailo, https://github.com/stubailo/vscode-ignore-gitignore is a decent workaround for now but this shouldl really be in core.

I think IntelliJ IDEA nailed this:

.gitignored files and folders are grayed out by default in File explorer
.gitignored files are automatically added to the projects "excluded" list

this means they do not participate in Search, Replace, Open File, Open Recent Files, Find symbols etc.

however, if you actually spell the file name (or if the file cannot be found in the current non-excluded project), it will switch to looking across all files in the project, including the ignored ones.

Searching for a file, there are matching files in non-ignored files/folders:

mobx.js does not exist in the non-ignored files, switch to full-project search (ignored files are still grayed out)

Hoping to get it in for search in this release, via moving search to ripgrep: https://github.com/Microsoft/vscode/issues/19983
Once we have that, it might be possible to use ripgrep's highly optimized gitignore code to support it in the file explorer as well. The problems with putting the patterns in files.exclude is that the syntax is not the same, and that it doesn't support negative patterns, and performance for large gitignore files could also be an issue.

@roblourens sounds great and I understand the issues. I'm looking forward for the next release.

Ripgrep search landed in today's Insiders, with .gitignore support enabled by default! Set "search.useRipgrep": true to try it out. There will likely be bugs... .gitignore support will be configurable later but I'm not sure how yet.

@roblourens thats great. Going to check it out and see if I can spot bugs for now.

@roblourens this is awesome, thank you!

@roblourens should we close this one given ripgrep work landed (release notes)?

But not file explorer yet. Issues like #13535 have been dupped into this one.

I wasn't sure since it has a lot of discussion about gitignore for the file explorer too. I think it makes sense to close this and start a new issue for that though.

The Ripgrep support is great, thank you for that! Can it be used for Cmd-P searching also? (It seems not, since I still get noise there if I don't configure the files.exclude setting to exclude them).
(Sorry to pollute this issue with a somewhat unrelated question, please point me in the right direction and I'll shut up. 😛)

Not yet, I've got an issue for it (which I just opened) - https://github.com/Microsoft/vscode/issues/24074

:clap::clap::clap::clap::clap::clap::clap::clap::clap:

@roblourens just curious: why was this closed? as far as I can tell it was never resolved.

It was implemented for 1.11 - https://github.com/Microsoft/vscode/issues/78#issuecomment-290939774

@roblourens Why is this closed? It is solved for searchs yes, but it's not solved for explorer and there is not an option to expclude files in the explorer tree from gitignore. Is there any other issue for the explorer topic?

Graying out gitignored files is implemented in 1.18, and hiding them can be tracked by https://github.com/Microsoft/vscode/issues/23804

authors: GarethOates Stanzilla Tyriar ZombieProtectionAgency apmeyer asotog bpasero danderson00 db2k denieler dmitriid egamma fbnlsr hashhar jamesdixon jhm-ciberman jonatassaraiva luisrudge mquandalle nchammas octref paulcbetts perlun rjmunro roblourens samuelt1 stubailo therealkenc tito v3ss0n zwacky


text:
VSCode touches file twice when saving file

VSCode Version: 1.3.1
OS Version: Windows 7 Enterprise 64-Bit

Steps to Reproduce:

NodeJS watcher on file (e.g. watchify with browserify)
Update function gets called twice.

When editing the file with notepad, the watcher only fires one update.
Thanks for the great tool!! :+1:

@bpasero @weinand any udpates?

@joaomoreno since you are looking into this area: do you have any insights into this issue?

Yeah something is definitely off here. Here's a process log of a simple save in Windows:

There are a total of 13 CreateFile events, when only one is actually a Write operation. The second watch fire might be due to the Generic Read operation... but I'm just speculating here. All other operations are Read Attributes, which seem to relate to stat calls.
One interesting optimisation to be done here is to call fs.open and use the file descriptors to call operations such as fs.write, instead of relying in the higher level functions such as fs.writeFile, which create many CreateFile lower level operations.

Hey, I just found out that the issue could be related to the way how windows handles read and write implementations and the nodeJS implementation of fs.watch.
http://stackoverflow.com/questions/12978924/fs-watch-fired-twice-when-i-change-the-watched-file
http://stackoverflow.com/questions/12978924/fs-watch-fired-twice-when-i-change-the-watched-file

I think this is nothing we can prevent because the file gets truncated before the write and then written to. We use fs.writeFile() (same as other editors using node.js) and if this results in too many file events, I suggest to file an issue against node.js.

This is expected as outlined in https://github.com/nodejs/node/issues/6112 and I do not think changing to other fs primitives would change this.

This could be prevented by creating temporary and then moving it over original (gedit does it this way).
There obviously are cases where this does not work but it would be great if that was a configuration option or if it tried to use renaming approach first and if it fails use current approach.

authors: ViktorHofer bpasero joaomoreno jskorepa weinand


text:
Default Markdown language configuration

Changes

use new autoClosingPairs grammar
add `, <> to autoClosingPairs
add surroundingPairs

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thanks! Should be in the next VScode 1.14 insiders build once those start up again

I think we need to remove ` as an autoclosing pair. It makes typing fenced code blocks pretty annoying

agree with you

source: gharchive/pull-request

authors: mjbvz msftclas neilsustc


text:
Electron 4.0.x

1

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: wjm97 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


text:
docker-compose fails on ubuntu agent "invalid reference format"

I am running a vsts-agent inside a kubernetes cluster. (microsoft/vsts-agent:ubuntu-16.04-docker-18.06.1-ce-standard).
When I try to run a build step from azure pipelines docker-compose exits with the following error:
Service 'xyz' failed to build: Error parsing reference: "microsoft/dotnet:2.1-aspnetcore-runtime AS base" is not a valid repository/tag: invalid reference format /usr/local/bin/docker-compose failed with return code: 1
The same build step executes without problems when it is run on a windows build agent.

The multistage build syntax requires a minimum version of the docker daemon on the host (https://docs.docker.com/develop/develop-images/multistage-build/)
Are you running in AKS, some other hosted K8s service, or is this on minikube/Docker-for-Windows (with K8s orchestrator)?
You should be able to run docker info on the machine where the agent is running or just as a step in your build, and see if the server version is high enough. Im pretty sure this isnt an issue with these images but I can investigate if your server version is indeed up to date.

authors: dakale sleppin

repo: Microsoft/vsts-agent-docker


text:
VS Test Agent Deployment - Failing with the error "Cannot find a process with the name 'DTAExecutionHost'"

I'm trying to run functional tests on a test machine from a VSTS build definition. I have an issue with the  VS Test Agent Deployment task (version 2.* using VS 2017). This task fails with the following error:

Error occured on '<my_test_machine_hostname>:5985'. Details : 'The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Cannot find a process with the name "DTAExecutionHost". Verify the process name and call the cmdlet again.'. For troubleshooting, refer https://aka.ms/remotevstest.

Here is the sanitized version of the full console output of the execution of this build task
BuildConsoleOutput_sanitized.txt
I already tried:

Rebooting the test machine
Uninstalling VS Test Agent and having it installed again as part of the execution of the Deployment task.
Executing Enable-PSRemoting command.
Including test user account in the Administrators group of the test machine.
Running the build while having test user logged in to the machine (via RDP).

Is there anything else I can try to solve this issue?
Many thanks
Max

We are experiencing the same issue using the same task and agent versions.
The only difference is that the deployment task fails for us and tests are not ran.
Step log:
tasklog_6.txt

Can you share testagentconfig.log file at devops_tools@microsoft.com. You will find the file in %temp% folder in test agent machine. Please share the build logs as well with system.debug set to true under in build definition.

Same issue. Agent version is 15.3.26730.8

Can you please try using Admin account for running the tests instead of different account? This should unblock. We have tracking bug for the same.

This issue is getting addressed here: https://github.com/Microsoft/vsts-tasks/pull/5089
It will be available with next task release. Closing this issue.

Already running under admin
Sent from my Sony Xperia™ smartphone
---- Nitin Gurram wrote ----
This issue is getting addressed here: #5089https://github.com/Microsoft/vsts-tasks/pull/5089
It will be available with next task release. Closing this issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vsts-tasks/issues/4982#issuecomment-325347764, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZKNQjt-3lx-73Px4-A6p-quAs_t-u5uks5scrssgaJpZM4OvwXl.

authors: iangavr mizbrodin nigurr tanvi-soni xenalite

repo: Microsoft/vsts-tasks


text:
.Net Core Tools Installer Version Issues

Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Environment

Server - VSTS
Agent - Hosted

Issue Description
When attempting to install the .Net Core 2.1-rc1 SDK following the help window information (below).
Specify exact version of .NET Core SDK or runtime to install.
Examples:

To install 1.0.4 SDK, use 1.0.4
To install 1.1.2 runtime, use 1.1.2
To install 2.0 preview 2 runtime, use 2.0.0-preview2-25407-01

For getting more details about exact version, refer here
Easy enough, in the version field enter "2.1.0-rc1".  Fire up the build and it fails (see Error logs below for details).  Turns out he correct version number for 2.1-rc1 is actually: 2.1.300-rc1-008673.  So either the help doc is wrong or the URL being assembled is wrong.
Error logs
2018-05-23T12:27:47.2062395Z dotnet-install: Payload URLs:
2018-05-23T12:27:47.2063153Z dotnet-install: Primary - https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.0-rc1-final/dotnet-sdk-2.1.0-rc1-final-win-x64.zip
2018-05-23T12:27:47.2063558Z dotnet-install: Legacy - https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.0-rc1-final/dotnet-dev-win-x64.2.1.0-rc1-final.zip
2018-05-23T12:27:47.2063904Z dotnet-install: Repeatable invocation: .\install-dotnet.ps1 -Version 2.1.0-rc1-final -Channel LTS -Architecture x64 -InstallDir
2018-05-23T12:27:47.2065740Z Downloading .NET Core package from primary URL: https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.0-rc1-final/dotnet-sdk-2.1.0-rc1-final-win-x64.zip
2018-05-23T12:27:47.2087237Z Downloading: https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.0-rc1-final/dotnet-sdk-2.1.0-rc1-final-win-x64.zip
2018-05-23T12:27:47.6639294Z Failed to download .NET Core package using primary URL. Error: Error: Unexpected HTTP response: 404.
2018-05-23T12:27:47.6640071Z Downloading .NET Core package from legacy URL: https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.0-rc1-final/dotnet-dev-win-x64.2.1.0-rc1-final.zip
2018-05-23T12:27:47.6660595Z Downloading: https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.0-rc1-final/dotnet-dev-win-x64.2.1.0-rc1-final.zip
2018-05-23T12:27:47.9169101Z Failed to download .NET Core package using legacy URL as well. Error: Error: Unexpected HTTP response: 404.
2018-05-23T12:27:47.9245351Z ##[error]Failed to download .NET Core package. Please ensure that .NET Core sdk of version 2.1.0-rc1-final exists. Check out: https://github.com/dotnet/core/blob/master/release-notes/releases.csv

When .NET Core SDK 2.1.0 RTM version will be available on VSTS hosted machine.

This is dupulicate of #7032. You can find the exact versions to specify there. We will be working on it to make sure that it is more natural.

@gencebay we are planning to roll it out soon. In the mean time, you can use the installer task.

authors: gencebay sachinma twurm


text:
Integration Test - Release - 2019/03/12 08:30:22

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#backlog'

#pri2

#assign PRMergerTest1

#assign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#reassign PRMergerTest2

GitHub user PRMergerTest2 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#reassign NonAllowedUser

NonAllowedUser is not a valid GitHub ID, or is not a collaborator on this repo.

#please-close

repo: MicrosoftDocs/CSIDev-Public


text:
Integration Test - Release - 2022/03/11 05:10:05

Auto create for integration test. IssueCommandFlow

#pri1

Just type '#pri3'

#pri2

#pri3

#assign PRMergerTest1

#assign NonAllowedUser

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

#reassign PRMergerTest2

#reassign NonAllowedUser

The following users don't have valid GitHub IDs, or are not collaborators on this repo: nonalloweduser

GitHub user PRMergerTest2 has been removed from the MicrosoftDocs organization, so they were automatically removed as an assignee.

#please-close

#unassign PRMergerTest1

#unassign NonAllowedUser


text:
Update fix-element-ids-sql-patch-script-for-ax-2012-r2-cu6-upgrade-sc…

…enarios.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamicsax2012-technet/fix-element-ids-sql-patch-script-for-ax-2012-r2-cu6-upgrade-scenarios.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


text:
QuickViewOfficeFilesEnabled does not support Intranet files

[Enter feedback here]
For the policy: QuickViewOfficeFilesEnabled
Currently the feature does not support for Intranet files that cannot be accessed via Internet, please make it clear in doc to avoid confusion.
Thank you!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 198c6f64-9e5c-f18e-8439-8d0d11d4228d
Version Independent ID: 83f32be1-063c-284c-dfdc-6b5976a5b7cc
Content: Microsoft Edge Browser Policy Documentation
Content Source: edgeenterprise/microsoft-edge-policies.md
Product: microsoft-edge
GitHub Login: @dan-wesley
Microsoft Alias: stmoody

@Nii-co Hello - Recently the policy documentation for QuickViewOfficeFilesEnabled was updated and specifically calls out the files need to be publicly accessible.
Here is the description: Allows you to set whether users can view publicly accessible Office files on the web that aren't on OneDrive or SharePoint. (For example: Word documents, PowerPoint presentations, and Excel spreadsheets)
Thanks!

authors: Nii-co Y-Kelly

repo: MicrosoftDocs/Edge-Enterprise


text:
More specifics on domain?

"Type the domain that you want to use with the geo location" - wondering if you could provide more specifics here.  For instance, is this our domain.onmicrosoft.com?  Is is this our on-prem domain name?  Does it need to be a unique domain per satellite location?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3d41ff16-b5cc-d2d2-6bb9-2134a0fafcd9
Version Independent ID: ebb5ff30-995f-92ff-f536-4386a7817b5f
Content: Office 365 Multi-Geo tenant configuration
Content Source: Enterprise/multi-geo-tenant-configuration.md
Service: o365-solutions
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

You need to enter a namespace for your satellite location (geo) and assign it the unique URL prefix:

@jvplopper  - Thank you for submitting feedback.
From our understanding, the issue you raised has been answered by VLG17. If you feel it hasn't been resolved, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

authors: VLG17 jvplopper mypil

repo: MicrosoftDocs/OfficeDocs-Enterprise


text:
Broken link

Link on "choosing PHS" is broken, it gives a 404

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1bd2f66d-c853-21ff-7f74-ccb1359af4e1
Version Independent ID: 807303e4-fbf8-ad2c-de8a-5ed65ad9216e
Content: Hybrid identity and directory synchronization for Office 365
Content Source: Enterprise/plan-for-directory-synchronization.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@fbrusa This has been corrected. Thanks so much for letting us know.

authors: JoeDavies-MSFT fbrusa


text:
Connection Information

Why does every powershell reference in Microsoft documentation omit the Connection command that must be used prior to the powershell script that is being referenced?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 719591af-cbcc-669e-a4c3-f36f223e7381
Version Independent ID: d1c0f978-69e3-cbce-a993-3ffd3016ba6b
Content: Create SharePoint Online sites and add users with Office 365 PowerShell
Content Source: Enterprise/powershell/create-sharepoint-sites-and-add-users-with-powershell.md
Service: o365-administration
GitHub Login: @JoeDavies-MSFT
Microsoft Alias: josephd

@Dodge1350 The instructions to make the connection to SharePoint Online are linked to from the "Before you begin" section at the top of each article.


text:
Test breadcrumb fix

This is flagging 2000+ broken link issues in the Broken link dashboard.

@JohanFreelancer9

@traya1 Can you review this change? Thanks

@beccarobins - Merging the PR now. Let me know if that resolves the broken link issues. More than happy to review/merge PRs to help resolve that issue.

authors: beccarobins get-itips traya1 yogkumgit


text:
Under new SharePoint admin center -> Settings, there is no "classic settings page" option

Also I cannot find how to  show or hide the Create site command.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b29978b1-a400-bacb-1330-55ed3d652053
Version Independent ID: eae9fd16-57fc-1a80-3ce9-9b34b68eb1e0
Content: Manage site creation in SharePoint - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/manage-site-creation.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

@legendgod Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

authors: legendgod scanum

repo: MicrosoftDocs/OfficeDocs-SharePoint


text:
Two prerequisite links are same

Obtain organization's subscription and user licensing... and assign permissions... are same links. Is this correct?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 2bc431d8-32c4-957d-9b3b-84bee4778ca5
Version Independent ID: 2bc431d8-32c4-957d-9b3b-84bee4778ca5
Content: Search the audit logs for app management events - Microsoft Teams
Content Source: Teams/audit-app-management-activities.md
Service: msteams
Sub-service: teams-apps
GitHub Login: @ashishguptaiitb
Microsoft Alias: guptaashish

Hi @geektocore , thanks for sharing this issue. I've updated the docs to point these to the respective sections in the same article. Closing this issue now.

Ah! Thanks.

authors: ashishguptaiitb geektocore


text:
Allow Chat in Meetings Setting

In this document this is listed as coming soon and under "Content Sharing" section. This is now available and is part of the "Participants & guests" section.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dc665475-f843-e4c1-0ca6-0b83873abb54
Version Independent ID: 95d32598-c920-ed5c-d665-69394528ca27
Content: Manage meeting policies
Content Source: Teams/meeting-policies-in-teams.md
Service: msteams
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

@MikeParker365 Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@MikeParker365 Thank you for reaching out. Are you suggesting removing the 'coming soon' from the document.

@MikeParker365 We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

Not sure if commenting will re-open this, but yes this feature is available so would suggest removing coming soon.  It is also not a per organizer setting, but a per user setting.  If chat disabled users can view chat in the meeting but not contribute.  If enabled users can chat.