5 ms·
Prelude includes and sets up the automatic activation of helm, projectile, ido, magit, and a fairly standard set of modules for languages like ruby, python, c,
by fennecfoxen 6y ago
Prelude includes and sets up the automatic activation of helm, projectile, ido, magit, and a fairly standard set of modules for languages like ruby, python, c, rust, js, css, html, xml, shell, scheme, (haskell, latex, erlang... etc etc)
If you have these set up already, and like the way you have them set up, don't switch. Instead, consider whether you'd benefit from crux, which is where they moved all the formerly unique-to-Prelude stuff:
https://github.com/bbatsov/crux https://github.com/bbatsov/crux
- cmrdporcupine 6y agoThanks. I've been wondering if I should invest the time to learn magit. It looks compelling, but deep and complicated.
- FPGAhacker 6y agoYou should definitely give it a try. The point of magit is to improve the git experience, not make it more complicated.
- cmrdporcupine 6y agoCool. With my remote work situation I've had to give up on local IDEs etc. and am back to emacs (with LSP for C++) so I am going to try to spend some effort to get it to a place where I'm more productive in it.
- narwally 6y agoThere's surprising little time you need to invest before magit starts paying back by decreasing the time you would have previously spent looking at the git documentation for the operations you don't use very often.
- trey-jones 6y agoAgreed. magit is one of the best pieces of software that I've encountered. Well-deserving of the "porcelain" moniker. Very intuitive, and you can always fall back to CLI if you need to.
- fennecfoxen 6y agoAll you really, really need is to run magit-status (bind it to a key for convenience) from any `cwd` in your project, and you get a snazzy overview of your outstanding commit. Then hit ?. Should be reasonably clear from there, at least to get started. If you get confused just go back to the CLI: it's easy to go back and forth, no magic.