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
VS Code UI has mistaken "chord" to mean sequence #89895
Comments
(Experimental duplicate detection)
|
Why don't you just put all of your problems with VS Code into one issue Plus as I said in #89899 "We're programmers, not spell checkers" So you can stop complaining about bad grammar. Or fix it yourself and make a PR |
I prefer to follow good practice - and the guidelines. "File a single issue per problem"
This isn't a spell-check issue.
This isn't a complaint - it is an defect report. And this issue isn't about grammar. |
I'm not sure I understand your issue. |
There's the issue. That's not what chord means in English (British or American). I'd guess the author of this text is not a native English speaker.
And that's not true. What is true, is that another keypress or chord is needed to complete the sequence. |
Could someone please reopen this issue please? It was closed by a contributor who said "I'm not sure I understand your issue." since which he/she has been given further information to help him understand it. |
Hi @chrisjj, Sorry to not get back to you. Technology often stretches the definition of English words to explain new ideas or features. VS Code uses "chord" in this way and so far it has resonated with most users. I don't think it is necessary to change the Status bar text. |
The existing meaning of chord in keyboard technology is far from new. See Wikipedia https://en.wikipedia.org/wiki/Chorded_keyboard . The fact the term may be new to some VS Code users is a poor excuse for misusing it, miseducating them and degrading accessibility to experienced users. |
e.g. status bar
The program isn't waiting for the second key of a chord, It is waiting for second key (or chord) of a sequence.
EDIT: Further instance:
The text was updated successfully, but these errors were encountered: