Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New setting to allow Quick Open dialog to ignore "files.exclude" setting #193739

Closed
espenja opened this issue Sep 21, 2023 · 2 comments
Closed

New setting to allow Quick Open dialog to ignore "files.exclude" setting #193739

espenja opened this issue Sep 21, 2023 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@espenja
Copy link

espenja commented Sep 21, 2023

Projects today are littered with different settings files, for example .eslintrc.json, tsconfig.json, etc.
Most of the time we don't need to deal with these files, so to have a clean workspace where my Explorer only shows the files and directories I am interested in, I have added all these settings files to the "files.exclude" setting. My workspace is now clean, and I can focus on the files that matter.

However, when I do need to make the occasional change to one of these "hidden" files, I want to be able to open them without going into my settings and manually removing or commenting the line containing the file I want to access, just to be able to access it. I didn't expect the Quick Open dialog (ctrl+p default) to also follow the "files.exclude" setting.

Could we have a setting to, or somehow, allow the Quick Open dialog to ignore the "files.exclude" setting.
This would allow us to have a more "zen" experience with the Explorer, but still be able to access hidden files we know are there.

@TylerLeonhardt
Copy link
Member

/duplicate #15604

@vscodenpa vscodenpa added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 25, 2023
@vscodenpa
Copy link

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

Happy Coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Nov 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants