Skip to content

feat: Add text mode for showing alphanumeric keys as text#437

Open
80avin wants to merge 1 commit intomulaRahul:mainfrom
80avin:feat-text-mode
Open

feat: Add text mode for showing alphanumeric keys as text#437
80avin wants to merge 1 commit intomulaRahul:mainfrom
80avin:feat-text-mode

Conversation

@80avin
Copy link
Copy Markdown

@80avin 80avin commented Feb 18, 2026

Context: I had to demo a vim session but seeing the alphanumeric keys as keycaps is very unintuitive.

This PR adds a text mode, in which, the text is shown as - text, not keycaps.

Also, it changes the default behaviour of / key, which was treated as ? in normal mode and / in shift mode, while in reality it is mostly opposite.

(ignore the low quality video - happened as artifact while converting mp4 to gif)
keyviz-demo

Since the feature was unasked, feel free to reject the PR.
And if you like the idea, I would request to add a proper "Vim mode" which renders all commands as vim renders shortcuts.

@JereNwa
Copy link
Copy Markdown

JereNwa commented Feb 22, 2026

As for the "/" thing, there's a feature that you can enable that I think might help.
Screenshot 2026-02-22 at 06 23 10
However, if you're going to add this feature, I recommend having the spaces actually show as spaces instead of having the " ﹈ " character appear.

@chan-yuu
Copy link
Copy Markdown

I really like this feature, could you please resolve the conflict of interest in this branch?

@80avin
Copy link
Copy Markdown
Author

80avin commented Apr 16, 2026

@JereNwa

  • the Symbol setting doesn't help. It changes not only / / ? but also other symbol keys while the issue was / key was at wrong shift level. Example, in normal scenario, pressing / would type / but showed ?
  • The character was added delibrately as the usual space does not appear when pressed alone. In neovim, we commonly press two spaces and that would show in popup, which is visually indistuingishable.
    If you have better suggestion, let me know.

@80avin 80avin force-pushed the feat-text-mode branch 2 times, most recently from 32ed11b to b07d7ef Compare April 18, 2026 11:32
@80avin
Copy link
Copy Markdown
Author

80avin commented Apr 18, 2026

I have rebased the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants