svd_bin VS marginalia

if anyone's interested in "independent" vim keybindings, made to work same in both insert and view modes (and a few different terminals), this is what i use for over.. 25years (?) Basically, few keys like old DOS PE2.exe or (later) e3.exe, and the like, then adding more with years. Like F2 for save, F3 for abandon, Ctrl-F/A for find forward/backward etc. Plus some other stuff that turns vim into kind-a IDE (grepping etc).

https://github.com/svilendobrev/svd_bin/blob/master/qini/_vi...

have fun

(ah, and the dual/multi mode-ness of vim adds extra layer inside it - making say ctrl-U to do undo always isn't that easy)

Each of those layers can vary, in different distro's, terminals, versions of same thing, etc. Especialy each and every (X-)terminal-thingie having different idea of how to map (or not) ctrl-F2. Some of them going back to the 197x ..

i have tried to make myself a one-mapping-fits-all (say, pressing F2 does ls -alF in terminal+shell, and saves-the-buffer in vim, no matter what/where/when), collecting variants and combinations for last ~25+ years - incl. linux-console and even dos mapping.. and it works mostly.. but still, no silver bullet.

see the qini/ folder in

https://github.com/svilendobrev/svd_bin

everything may be remapped to your liking.. eventually. YMMV.

ciao

if anyone finds any of these useful...

https://github.com/svilendobrev/svd_bin (terminal + sh setup , version-control, lots of commands for this or that)

https://github.com/svilendobrev/svd_util (python stuff)

Check out marginalia[1]. Whenever you press M-x, it will pop up a buffer showing all the commands (with most recent ones on top) along with their keybindings and a brief description of what they do.

Embark[2] is also cool. It will show all the possible commands relevant to where the cursor is at that moment. I bind it to C-c a.

[1] https://github.com/minad/marginalia

Then there is Marginalia which is IMO essential

marginalia. Informative annotations for minibuffer completion candidates, co-written with u/minad-emacs.

Wow, interesting that my response is getting down voted. It seems not enough that I give away my work for free. Nevertheless I appreciate support from the community, as other Emacs package developers. The support is actually helpful. To clarify, publishing my configuration would translate into quite a bit of work, requiring separation of private and public bits.

marginalia for extra info in the minibuffer

There seems to be some problem with straight not correctly installing or updating compat. See these issues on Marginalia and Embark where straight seems to not install Compat.

Note that I contribute to Emacs core itself from time to time but the process is discussion-heavy and thus time consuming. If you are familiar with the completing-read API, you may know the annotation-function of completion tables. The name already tells that this function just adds annotations to the completion candidates. The Marginalia package (written by /u/oantolin and me) provides such annotations. A similar function is the group-function, which groups candidates in subsets and adds titles above the subsets. I wrote the patch which added this feature to Emacs. It is now supported by default completion, Icomplete, Vertico and maybe other UIs. The initial implementation was done in the earlier Selectrum package, and a little later in Vertico.

At the end of the year, I am happy to announce the stable Vertico 1.0 and Marginalia 1.0 releases. Vertico is a minimalist, yet flexible and responsive vertical completion UI. Marginalia provides helpful annotations for many completion contexts. Both packages have been solid for a while but I rather let things mature slowly. These releases finally put the stamp "stable" on these two packages. I expect the other members of the package suite to follow soon after. Both packages have been updated recently to support the newest Emacs 29 features. They are compatible with Emacs 27, 28 and the upcoming 29.

I) I started out trying to implement this using marginalia, like the consult commands, but quickly concluded that this wasn't the way to go here... please correct me if I'm wrong and there is more from these packages I could make use of. I also try to make use of as much of the citar codebase as possible, but have found it difficult so far: a lot seems too specific for bibliographic entries.

I can't find anything that seems to discuss them in detail, but Marginalia is a package that applies them widely in completion. And here is a simple example for customized file completion.