3 ms·
Instead of attempting to change ALL tools to accept a config file in a non-standard location which is never going to happen, and will just lead to having files
by zarzavat 3y ago
Instead of attempting to change ALL tools to accept a config file in a non-standard location which is never going to happen, and will just lead to having files in both locations, just recode the file browsers to optionally display config files under a virtual directory. There’s surely fewer file browsers than tools.
- programmarchy 3y agoThis was my thought as well. VS Code already has files.exclude in .vscode/settings.json
- 111111IIIIIII 3y agoYeah that's what I use when I care enough
- Drblessing 3y agoThis is great! I didn't know about it. What files have you added?
- 111111IIIIIII 3y agoI actually have an extension that adds a little expandable section called "Hidden Files" at the bottom of the explorer pane, where I can open it and add a check beside the files I want to hide. In some projects, I change it at leisure, which usually means I'm hiding any files that never have any bearing on my day to day work. Sorry I don't remember the exact name of the extension.
- Drblessing 3y agoThanks!