which-key.nvim icon indicating copy to clipboard operation
which-key.nvim copied to clipboard

feature: assign separate highlight to buffer-local keymaps

Open chrisgrieser opened this issue 11 months ago • 13 comments

Did you check the docs?

  • [X] I have read all the which-key.nvim docs

Is your feature request related to a problem? Please describe.

While groups and keymaps are easily distinguishable by the icon for groups and simply having different highlight groups, buffer-local and global keymaps do get the same highlight group WhichKeyDesc, and are thus not distinguishable.

Showcase

(here, the first one is buffer local to markdown files)

Describe the solution you'd like

Assign a separate highlight group to buffer local keymaps.

(I'd even argue that distinguishing buffer-local and global keymaps is valuable enough, that they should by default have different colors, but that's probably a different question.)

Describe alternatives you've considered

The only two mechanisms for differentiating buffer-local keymaps from global ones are the sorting and require("which-key").show({ global = false }). While they technically work, they are rather inconvenient methods for checking if a mapping is buffer-local.

Additional context

No response

chrisgrieser avatar Dec 06 '24 20:12 chrisgrieser

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Jan 09 '25 02:01 github-actions[bot]

Comment for the bot

chrisgrieser avatar Jan 09 '25 05:01 chrisgrieser

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Feb 10 '25 01:02 github-actions[bot]

Don't

bew avatar Feb 10 '25 07:02 bew

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Mar 13 '25 02:03 github-actions[bot]

Don't

bew avatar Mar 13 '25 07:03 bew

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Apr 13 '25 02:04 github-actions[bot]

Don't

chrisgrieser avatar Apr 13 '25 04:04 chrisgrieser

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar May 14 '25 02:05 github-actions[bot]

still not?

bew avatar May 14 '25 02:05 bew

the most useless + annoying bot ever 🤦🏻

disrupted avatar May 14 '25 12:05 disrupted

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Jun 14 '25 02:06 github-actions[bot]

dalila...

bew avatar Jun 14 '25 06:06 bew

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Jul 30 '25 02:07 github-actions[bot]

Not stale

chrisgrieser avatar Jul 30 '25 04:07 chrisgrieser

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Aug 31 '25 02:08 github-actions[bot]

Not stale

chrisgrieser avatar Aug 31 '25 04:08 chrisgrieser

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Oct 02 '25 02:10 github-actions[bot]

Just stop?

bew avatar Oct 02 '25 05:10 bew

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Nov 02 '25 02:11 github-actions[bot]

Bump

chrisgrieser avatar Nov 02 '25 03:11 chrisgrieser