-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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
VSCode disappear from candidate list to open text file in Linux #214741
Comments
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.90.0. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding! |
Well, it does 1.90.0 actually. |
Ovear
added a commit
to Ovear/vscode
that referenced
this issue
Jun 10, 2024
VS Code is a versatile text editor, and it's essential to properly declare its capabilities. Not only was plain text files be recognized as text/plain, but also coding files like .go, .php, .py, etc., which are a primary focus of VS Code. We definitely need these file types to appear in the candidate list when opening files.
Ovear
added a commit
to Ovear/vscode
that referenced
this issue
Jun 10, 2024
VS Code is a versatile text editor, and it's essential to properly declare its capabilities. Not only were plain text files be recognized as text/plain, but also coding files like .go, .php, .py, etc., which are a primary focus of VS Code. We definitely need these file types to appear in the candidate list when opening files.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Does this issue occur when all extensions are disabled?: Yes
This change was introduced by PR #209510. I am unsure why the original poster claims that "This software is not a plain text editor," as it actually is.
If I understand correctly, this PR aims to address issue #114425. Why then was "text/plain" removed from the MIME list? The issue should be resolved by removing "inode/directory" only instead.
Introducing this controversial and unrelated side effect into a PR meant to fix a bug does not seem convincing.
Additionally, it seems I am not the only one questioning this. There are also doubts expressed in the commit log, but no answers have been provided. Check commits here: f1c0071
P.S. I forgot to mention that this change also affects coding files like
.py
,.go
, and.java
, as most of these files are recognized as "text/plain".The text was updated successfully, but these errors were encountered: