helpful VS marginalia

If you want to programmatically create files, write to them, etc, then read the fine manual, it comes with your Emacs, has index, search and web-like navigation. It is well worth your time investing in looking up the manual, both for Emacs and for Elisp. You access the manual via C-h i. Another good thing to learn how to use is Emacs built-in help. As a minimal basic, C-h f will display information about functions, and C-h v will display the documentation for variables. You can also see where things are declared, open the source code, etc. A good alternative to built-in help is Helpful, which I suggest installing and start using too.

It tweaks Emacs GC. You can run M-x describe-variable while your cursor is at gc-cons-threshold to learn about it. If you opted-in for using "Vim bindings" (Evil mode), you can press K while in normal mode. Note that K doesn't run the describe- command in Doom, but it runs helpful-command from (https://github.com/Wilfred/helpful), which provides more context that describe- commands usually do.

The packages helpful and elisp-demos are super useful because they enhance Emacs' built-in documentation.

You can try to actually use helpful for a while. There was also a package with examples, I don't remember the name, perhaps someone else knows which I mean, that shows usage of a function where available. I remember using it and found it very useful for a while when I was learning elisp more actively. I still use helpful sometimes.

Once you got the hang of keybindings, which-key is a helpful extension (aka package) to Emacs. At this stage, there are other helpful packages and keybindings.

helpful for better help buffers

Since you seem interested, have a look at elisp-demos , too. It works in tandem with helpful.

Elisp Docs are fantastic they have documented everything while with CL most documentation is missing or only on the Web. With Emacs, one need to learn about C-h f (describe-function), C-h k (describe-key), helpful.el and elisp-demos and a new world opens. Terminology is always different, simple example: Microsoft terminology sounds like bullshit, to a Unix person.

Your primary source of knowledge will be the manual and the built-in discoverability (describe-* functions, or helpful) and of course reading the code. I'm not a manual person myself, but Emacs is one of the examples where it is truly excellent and has answers for almost everything.

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.