-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Display language identifier in Language Mode drop down #11977
Comments
Sounds like an easy enough area for a PR 👍 |
@mrmlnc happy to review a PR if you wanna give it a shot 👍 |
@bpasero I think I like the parentheses and dash for Configured Language better. I would also add some explanation in the upper right where now it just says "languages". Maybe "languages and language identifiers" or "languages (language identifier)" if we use parentheses. |
Another rendering would be to right align the language IDs on the right, same as we do it with the key bindings |
Reopening as I think we need to explain that language identifiers are in parentheses. Maybe changing the upper right text from "languages" to "languages (language identifier)" |
Makes sense. |
Many user settings need to know a language's language id. Examples include files.associations, emmet.syntaxProfiles, emmet.excludeLanguages. Some settings display the language id list in suggestions (ex. files.associations) but not others (ex. emmet.syntaxProfiles).
vscode-docs issue microsoft/vscode-docs#572 recommends documenting the most commonly used language ids but this list will be long and need to be maintained.
We could display the language id in the Language Mode drop down list. Perhaps in parentheses:
JavaScript (javascript)
C++ (cpp)
The "languages" message on the upper right of the dropdown could be changed to something like "languages (language identifier)" or expand to a full description of language ids.
This way the list will be scoped to only languages the user has installed and always up to date. The list will also be discoverable in the product and not require the user to search our doc website
The text was updated successfully, but these errors were encountered: