Mention F10 in the menu to make this feature visible
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Search the repository for the existing F10 menu shortcut and for status-bar or empty-buffer message rendering. Decide where the keyboard hint belongs, make it disappear when typing begins, and verify the menu remains accessible through F10.
Written by the indexing model from the issue text.
Description
Context:
I came across this issue on adding hotkey to open menu on headless machine that doesn't have a mouse.
https://github.com/microsoft/edit/issues/135
Key F10 was used to open menu, and issue was closed.
Problem:
F10 is great, but no where in the repo nor doc nor help in the edit itself mentions F10 can be used to open menu on machine that only have keyboard.
Suggestion:
There should be a text in the status bar saying something like "Press F10 to open menu".
Or at the center of page when edit command opened a brand new file, simialr to how VIM used to display a message when vim is started with just vim.
When user starts typing, the message should automatically disappear.
Illustration of the proposed help/tip message.
- Dominant language
- Rust
- Stars
- 14.6k
- Forks
- 735
- Avg merge
- 21h 38m
- Merged PRs (30d)
- 10
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/edit
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/edit#367 · 2 reactions ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
microsoft/edit#948 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 75/100
microsoft/edit#947 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microsoft/edit#928 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
microsoft/edit#904 · 2 reactions ·
Maintainers usually reply within 1 day
Similar issues
-
Change output crossing a compactsize boundary leaves the fee slightly below the requested feerateOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bitcoindevkit/bdk_wallet#578 ·
Maintainers usually reply within 8 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
521xueweihan/HelloGitHub#3832 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
canonical/opentelemetry-collector-operator#409 ·
Maintainers usually reply within 1 day