Ignore backup files in chrome debugger source tab - google-chrome-devtools

I am using Chrome DevTools and have mapped my local source tree. As a result, when I look in the Filesystem tab in the Sources tab, I can see all of my source files and all of my backup files.
The backup files are pure clutter: is there a way to hide them from the view?
I am not talking about black boxing: that prevents me from stepping into files that are actually used. I want to not see files that are not used in the list of files.
I want model.jsx.~1~ to not show up in this case. In general, any file matching *~ should be hidden.

As reported in the comments, this is not currently possible. I created an issue to request the ability.
https://bugs.chromium.org/p/chromium/issues/detail?id=883325

Related

Is there a way to collapse only files in VS Code’s explorer?

I work on a large project where large portions of the files are not in “leaf nodes”. There are many directories with subdirectories and a large number of files as well. This poor organization has made navigating the file tree an onerous exercise to say the least.
I’m wondering whether there is a convenient solution, native or in an extension, that allows the VS Code explorer sidebar to by default not show all the files in a directory that either has subdirectories in it or has them open. Instead it could have an item called Files which could be separately expanded/collapsed as if it were a subdirectory.
The program WinDirStat uses this approach by default, here is an image for reference. Notice how there is a section labeled “Files” to reduce clutter.
If this doesn’t exist as a setting or an extension, I suppose that’s not a bad idea for a project.

VS Code does not see existing file

Apparently VS Code does not list existing files in files dropdown (Ctrl + P command).
Here is what it shows:
As you can see, the file laravel-2019-09-26.log exists in the directory (left bottom), but not in the files dropdown. After I open this file from the Explorer tree, it starts showing in the dropdown.
Am I doing something wrong or does this happen for everyone? Or is this command supposed to show previously opened files only? If so, what is the way to quickly open any existing file in the workspace?
N.B: I have gone through this related question. No one has mentioned this problem, making me think that this might be specific to my machine.
Edit
For future readers, second answer provided by #michaelze is spot on. VS Code by default does not list files mentioned in .gitignore. You can change this setting by going to Settings panel (File > Preferences > Settings) and typing useIgnoreFiles. This will bring up two boolean settings named Use Global Ignore Files and Use Ignore Files. Turn off these two settings and all workspace files will start showing in the files dropdown. Works correctly as of version 1.38.1.
As those files are .log files, I assume, they are maybe mentioned in the .gitignore file? Maybe this can help you? Visual Studio Code - Automatic exclude based on .gitignore
The list you are seing when pressing CTRL + P is called recently opened. When you open one of the files, it was recently open, so it shows up. The CTRL + P menu also has a files results section that lists actual search results from the files you have in your workspace. None of your .log files are showing up in this section (hence the section is not visible).
The laravel-2019-09-08.log file is also missing from the drop down.
I was wondering if maybe the listing is capped to a certain number of files. Try to be more specific with your search. In my version of VSCode, I can search for files using multiple words. Maybe try searching for "laravel 26" to find the file you are looking for?

How can I search for a file in just one specific folder in VSCode when using a workspace with multiple folders?

I'm using the workspace feature of VSCode, with two projects, but it's annoying to search for a file in the front-end project and need to pass by back-end files to find the one I want.
I'm using ctrl + p to search for files.
How can I search for a file in just one folder with multiple projects opened in the workspace?
Yes thats possible: use a relative path: ./mySearchedProjectName in "files to include"-input
from HERE!
UPDATED answer to UPDATED question
The fuzzy file finder (CTRL+P or ⌘+P) somehow supports prefixing the filename with a folder, such as folder/filename to locate a file from a specific folder:
But, in my experience, the search is a bit lacking. For example, I find it usually can only find files this way if that file has been recently opened in your workspace. It also does not support regex.
The best thing that can be done is to enable including recently opened files by adding this to the workspace settings:
"settings": {
"search.quickOpen.includeHistory": true,
AFAIK, there is no other built-in way to filter the results. There are (still) open feature requests for this, like this Allow quick open to filter on folder names by typing folder name after the file. You can thumbs-up them to hopefully get them noticed.
ORIGINAL answer to ORIGINAL question
I don't know what you mean by "projects" since VS Code only has "workspaces" and "folders", such that you add folders to a workspace. I think you're already doing this, where each folder contains a separate set of codes.
With that said, the Search/Find panel has an area to specify files to include, where you can limit your search to a specific folder. For example:
Here I have 3 folders (proj 1-3) added to a workspace. I have 3 sample files with the same text.
When searching, you can set files to include to a specific folder (./proj2), so that the search results will be limited to that folder.
I've found the best solution to this for me (though it's still a sub-optimal one) is simply to run multiple VS Code instances, one for each folder.
It's a pain to start up, but once you get things going (and hopefully you're not restarting often on your dev machine, so this is less of an issue) it works perfectly: you can search for files with only the relevant ones showing up.
Also, if you want to reduce the start-up pain you can make a shortcut/alias/etc. in your operating system that starts both at once.

Prevent VS Code from opening all files in a folder recursively

I am currently using VS Code on a folder mounted through an SSHFS. The folder has subfolders with many jpg and other image files.
Logging all the files VS Code tries to open reveals it recursively touches all the files (doesn't read the content, just STATs them). This takes very, very long over an SSHfs mount and I can not cancel it without killing the editor (it won't even respond to regular closing).
During this, no files or directories can be opened (inside VSCode) and will show a loading spinner until VS Code has finally had it's way and checked all the files.
This behaviour only recently emerged, I can't pinpoint if any version beyond the current stable version has this behaviour.
I am thinking it might be the new searching engine, but I can't find out which part of the editor is doing it.
It looks like they just posted a fix for your situation:
Slow startup opening a large workspace over the network
you will need vscode v1.32.3

Chrome Developer Tools add a SINGLE file to workspace not folder

I'm doing some clean up work in the stylesheets. But there are some files that I don't want to touch by accident. So I don't want them to be editable. How can I add some files to the workspace but leave the rest of the files in the folder are not added.
Basically I want to achieve below;
DevTools technical writer here. It's not possible to choose which files are editable in Workspaces. The intended use of the feature is to persist any changes in a given directory to disk.
Maybe you'd prefer to use Local Overrides?
Also, a potential workaround could be to use chmod to disable write access on the files you don't want to touch...