Display command name in the status bar after a keybinding

[amgalan81mn]

when pressed second key then display command name for short time
ctrl+k was pressed, waiting for second key of chord... "code folding -> collapsed to level 2"

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• Emit first key chord when timeout or wrong second key chord (#15550)

[gjsjohnmurray]

Please clarify. Are you reporting a bug? Or requesting an enhancement?

[sandy081]

Why is it only for chord keys but also for all keys?

[amgalan81mn]

requesting an enhancement, just display what kind of combination pressed, the name of it.

…

On Sun, Dec 1, 2019 at 9:42 PM Sandeep Somavarapu ***@***.***> wrote: Why is it only for chord keys but also for all keys? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#85790?email_source=notifications&email_token=AF4GUFJHJSQCEIMUPNG6EOLQWO5L3A5CNFSM4JSZ7MSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFRJSHQ#issuecomment-560109854>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF4GUFPLRU2MUSXTWQKDKZTQWO5L3ANCNFSM4JSZ7MSA> .

[vscodebot]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[alexdima]

I have tried out the changes in PR #86524, but I have to be honest and say that I personally don't find this a useful addition to VS Code, it does not feel natural to me for the status bar to constantly echo and repeat the action I executed.

Are there other editors that do what is proposed here?

[vincentfiestada]

I assume this is trying to achieve some vim-like features around keybindings? But I agree that this doesn't seem very useful.

1. If I use a keybinding, I probably already knew what it was going to do.
2. If not, it may have been by accident, in which case should the command stay in the status bar long enough for me to notice? What if I accidentally use 2 keybindings in a row, then this feature doesn't help me at all. And wouldn't most users simply notice the accidental change and undo?
3. This doesn't help with feature discovery, unlike the command palette.

At the very best, this seems out-of-scope and should be implemented by an extension instead.

[gjsjohnmurray]

I concur with @alexdima and @vincentfiestada

If the goal is to answer the question, "hey, what did I just do there?" perhaps add a new OutputChannel, logging each command that gets executed. Then the interested user can view this in the Output tab of the Panel.

[alexdima]

If the goal is to answer the question, "hey, what did I just do there?" perhaps add a new OutputChannel, logging each command that gets executed. Then the interested user can view this in the Output tab of the Panel.

This already happens. When using the trace log level, each executed command is logged.

I have also presented this issue in today's standup and there was unanimous agreement that we don't want this feature, so I will close this issue for now as "out-of-scope".

[vscodebot]

We closed this issue because we don't plan to address it in the foreseeable future. You can find more detailed information about our decision-making process here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!