emacs-which-key VS prelude

I think which-key already solves exactly that: https://github.com/justbur/emacs-which-key

As for the "complicated keybindings general" -- I assume because remembering things like C-x C-s is hard because of the shifted keystrokes? I get that, and there is in fact a solution for less used keybindings which I love, called 'which-key' https://github.com/justbur/emacs-which-key

I would recommend installing the which-key package, which is a fantastic discoverability aid. If you ever want an example config to get some inspiration, I have one here: Emacs Bedrock

Make sure you have which-key installed and turned on. When using a keybinding that has a prefix (like C-x or C-c), it displays all the keybindings that start with that prefix.

which-key for the shortcut menus

there are some packages to help with the keybings, which-key shows a list of keybind and its command and (guru-mode)[https://github.com/bbatsov/guru-mode] enforces to use the "best" keybind, for exemple, it forces you to use C-n to move the cursor, blocking you to use the down key, and if you press the down key, it show a text in minibuffer to the best keybind.

Thanks for confirming, I think it's an issue in which-key itself: https://github.com/justbur/emacs-which-key/pull/166

If you haven't already, definitely check out the package which-key.

> even though I'm a terminal user ... I really like the discoverability of GUIs, and that's where a good GUI is unbeatable by CLI.

CLI has poor discoverability? Sure; but even on the terminal, discoverability can still be good:

A couple of nice examples of discoverability in keyboard-focused programs:

- emacs' which-key[0]; there's a vim port[1] too. This shows you (some) of the available keybindings for the next input, and a short label. So you don't have to remember what `SPC h p ...` or all the options under `SPC f...`.. but it still helps to recall that `SPC h` is for 'help' related commands, `SPC f` for file related commands.

- emacs' magit[2][3]. Magit is so good at discoverability, that I'd rate it as the best tool for using git with. I've learned more about git from using it.

[0] https://github.com/justbur/emacs-which-key

[1] https://github.com/liuchengxu/vim-which-key

[2] https://magit.vc/

[3] https://emacsair.me/2017/09/01/magit-walk-through/

Am I right in thinking this is quite similar to which-key?

> I forgot how absolutely horrible the new user experience is...

The bbatsov/prelude project was started in 2011 to help address that problem. I started using it not long after that, and it's been a joy to use ever since.

And by "started using" I mean I forked it on GitHub, stared personalizing, and then merging/rebasing from upstream ever since at my own leisure.

https://github.com/bbatsov/prelude

https://prelude.emacsredux.com/en/latest/

From 2011 to present, not everyone in the Emacs community feels bbatsov's Emacs Prelude makes the best/correct decisions, but given how long Emacs has been around and how large the community has been over time, what can you really expect?

It's certainly a lighter-weight starter kit compared to Doom Emacs and Spacemacs. (I'm not knocking those projects!). I've also looked at some of the newer starter kits mentioned in other comments here and previous HN threads; they seem okay to me, just reinventing a lot of the same "wheels" you'll find in Prelude but in a less refined form in many cases... such are the freedoms, joys, and trials of Free Software.

If I recall correctly, on my mac I had an issue with the meta and super keys. I had to rebind Meta to Cmd and Super to Opt. Im pretty sure I used Bozhidar Batsov's solution for this.

Another reason for you to stick to Emacs is Emacs Lisp. If you enjoy writing lisp you are not going to find a better piece of software written in any other lisp language. I prefer common lisp to elisp (alot!) but this is a fact in my opinion. Plus elisp is somewhat similar to common lisp and learning/appreciating the differrnces between the two will make you a better lisp programmer.

https://github.com/bbatsov/prelude/blob/master/core/prelude-...

I have based my emacs config on Emacs Prelude from u/bbatsov, because I did not trust starting from vanilla emacs.

When some days ago I decided to use org-mode again, I didn't use Doom Emacs, and it was the best decision that I've made. Instead, I used Prelude, which is a very simple and powerful Emacs config, and it's much less opinionated than Doom Emacs and Spacemacs. Then I disabled the Prelude theme, and combined it with Nano-Emacs. Now I have a very simple Emacs config, which provides me with some of the best tools, and also a very beautiful and elegant theme. I can change everything I want very easily, customized it to my needs.

How do you know? You said you want "fully setup" :) Prelude? Spacemacs? Your own version?

Thanks :)… it was originally heavily inspired by Emacs Prelude, but has since drifted quite far from it.