lispy VS hydra

Some killer features in Emacs, which I would recommend checking out, is imenu and movement by s-expression (functions like forward-sexp). These are built into Emacs and make navigating across or inside blocks of code very easy. I have also seen that lispy, which is usually used for Lisp code also supports Python. Again I can't speak to any specifics about how well these things work for Python devs.

While writing other programming languages with LSP, it formats the buffer once I hit save. Is there any way to make https://github.com/abo-abo/lispy do some equivalent behaviour?

Without any order magit, lispy and minions.

I don't know cider, but...I found lispy mode a revelation in making the easy, easier.

The level of interactivity in your emacs determines how easy trying emacs-lisp becomes. I suggest checking out https://github.com/abo-abo/lispy, it makes it easy to look up documentation (C-c 1 I believe) and evaluate S-expressions on the fly (keybinding is e). Also C-h f, C-h k, C-h v are always very helpful. Also check out helpful (the package), selectrum, marginalia, prescient, etc.

Emacs seems to attract quite a lot of people who want structural code editing. We now have * paredit * smartparens * evil-cleverparens * lispy * symex * combobulate (more?)

Obviously, we have packages like Paredit and Lispy, recently we got SymEx, but these are all for the Lisp family of languages, where syntactic redundancy is very high because of the homoiconicity.

You can also use Hydra for Emacs.[1] Once I discovered how to configure Hydra, I made it a habit to make one for every new major mode I need to use.

[1] https://github.com/abo-abo/hydra

Have you considered a hydra?

An Emacs specific example: I'm working on a few go projects at the moment and go requires recompilation after changes. Step one was finding auto-recompilers for my projects (I'm using both air and reflex in various projects). Step two was realizing that I spent a lot of time switching to the buffer where the output is printed, so I wrote a little hydra menu to make that easier. Then I found myself having to restart those processes each time I restarted Emacs, so I went digging and found detached to manage the processes. Then I got tired of having to hunt for where the detached output was displayed in my frame so dug into sidebars to manage the windows more effectively.

I think the goal of the hydra package is to provide such functionality.

I would I also encourage anyone who does not want to use modal editing to look into repeat-mode, hydras, and key-chord.

The C-c prefix is designed for you, the user, to use for your nefarious deeds. Some things that may help with both binding and knowing what key does what would be a menu such as hydras or transient menus (which apparently are part of Emacs now so that's new).

For the very same reason, I started to use hydras: https://github.com/abo-abo/hydra - see my config at https://github.com/novoid/dot-emacs/blob/master/config.org

Hydra lets you define mini-modes with limited scope.

general.el also works well with hydra.el. Here's my hydra for window operations - it activates when I press ,w: