Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Mappings can have custom description #536

Open
chama-chomo opened this issue Dec 25, 2020 · 6 comments
Open

Mappings can have custom description #536

chama-chomo opened this issue Dec 25, 2020 · 6 comments
Labels
enhancement

Comments

@chama-chomo
Copy link

This one is slightly related to #91, which is closed already.

Actually, it would be really convenient if there is support for a custom description of mapping commands:

At the moment a context menu might not look very helpful every time:

keys    command
gb      :{{ git_branch -- []; }}
gg      top -- []
gh      cd -- [~]
gl      :{{ git_log -- []; }}
go      :{{ fasd_dir -- []; }}
gp      :{{ git_pull -- []; }}
gs      :{{ git_status -- []; }}

Desired state:


keys     description                         command
gb       Change git branch             {{ git_branch -- []; }}
gg       Show system resources         top -- []
gh       Change current dir to ~        cd -- [~]
gl       Show git log                  :{{ git_log -- []; }}
go       Quick jump folder (fasd)       :{{ fasd_dir -- []; }}
gp       Get changes from remote       :{{ git_pull -- []; }}
gs       Show git status               :{{ git_status -- []; }}

A possibility to even suppress certain columns as configured by the user would be nice, too.
@gokcehan
Copy link
Owner

@chama-chomo Is this the same as #363 ? To be honest your explicit command name approach here seems like a good solution for this.

@chama-chomo
Copy link
Author

thx @gokcehan, this is only nice to have feature, I can live without it easily. On the other side, when it comes to some design decisions, I'd be happy if developers can take this into account. I think I will not be the only one, who would appreciate this small UI improvement.

@gokcehan
Copy link
Owner

@chama-chomo I agree I'm a little conservative when it comes to cosmetic features. I think this one requires adding a new syntax to our command definitions and I'm not a fan of changing the syntax. I can label the issue as enhancement and we can keep it open in case someone comes up with a clean solution for this.

@ndavd
Copy link

ndavd commented Oct 1, 2021 •
edited
Loading

Hoping for this to be added someday :)

@ilyagr ilyagr mentioned this issue Aug 24, 2022
Closed
@user529
Copy link

user529 commented Oct 24, 2024

I'd also vote for this feature.
I have several complex commands, and they are not easy to recognize quickly from the text. And some brief descriptions could be really helpful.

Of course, there can be many approaches to implementing this. But I have never tried programming in GO, so I won't provide things like PR in the near future. But I'm ready to share some ideas.
Perhaps at first, it would be easier to introduce a new token for descriptive mappings, something like:
DMapExpr = 'dmap' "Brief description" Expr

@og900aero
Copy link

I'd also vote for this feature. Plus, It would be nice if it could be set to show only the keybinding and the name of the associated action, and not the command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@gokcehan @chama-chomo @og900aero @user529 @ndavd
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy