You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
files.exclude allows users to define which things should be not in file explorer, should not be searched and not indexed.
They can still be opened using "file open".
'markdownDescription': nls.localize('exclude',"Configure [glob patterns](https://aka.ms/vscode-glob-patterns) for excluding files and folders. For example, the File Explorer decides which files and folders to show or hide based on this setting. Refer to the `#search.exclude#` setting to define search-specific excludes. Refer to the `#explorer.excludeGitIgnore#` setting for ignoring files based on your `.gitignore`."),
...(isWeb ? {'**/*.crswap': true/* filter out swap files used for local file access */} : undefined)
},
includes commonly used VCS' subfolders like .git, .svn, ...
The last commit there 1d9dc8b "web - filter out *.crswap via files.exclude" sneaked in the windows-only Thumbs.db (which I find a reasonable addition in any case), the previous fa0bc23 added CVS, with previous .hg and .svn additions.
I suggest to add more files there and while I initially had a bunch of files in my mind, including the list from the end, I've stepped down and suggest to at least add files ending with a~ because those are, over several systems and software, always temporary files #228981.
I'd like the community to:
vote for general addition of more entries, staring with **/**~
discuss which entries should be added, possibly including (this list is from a portable C build)
Users can override that (which then means to also include the default values wanted) in their settings (so workspace/user/machine scope), so files that are "only very seldom should be used in the UI" can still be included (for example if someone wants his Thumbs.db or TAGS files shown), but we should still consider the likelyness (.deps seems to also be "something .NET/C#, not sure if this is like .vscode which you want to have included by default, for example).
Entries like *cache* are likely bad, thinking of for example package names including it. But who should have .bak or .tmp files shown and searched...
The text was updated successfully, but these errors were encountered:
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
files.exclude
allows users to define which things should be not in file explorer, should not be searched and not indexed.They can still be opened using "file open".
Reasonably the default
vscode/src/vs/workbench/contrib/files/browser/files.contribution.ts
Lines 155 to 159 in 4c31caa
.git
,.svn
, ...The last commit there 1d9dc8b "web - filter out *.crswap via files.exclude" sneaked in the windows-only
Thumbs.db
(which I find a reasonable addition in any case), the previous fa0bc23 addedCVS
, with previous.hg
and.svn
additions.I suggest to add more files there and while I initially had a bunch of files in my mind, including the list from the end, I've stepped down and suggest to at least add files ending with a~ because those are, over several systems and software, always temporary files #228981.
I'd like the community to:
**/**~
Users can override that (which then means to also include the default values wanted) in their settings (so workspace/user/machine scope), so files that are "only very seldom should be used in the UI" can still be included (for example if someone wants his Thumbs.db or TAGS files shown), but we should still consider the likelyness (.deps seems to also be "something .NET/C#, not sure if this is like .vscode which you want to have included by default, for example).
Entries like
*cache*
are likely bad, thinking of for example package names including it. But who should have.bak
or.tmp
files shown and searched...The text was updated successfully, but these errors were encountered: