11–20 of 32 posts
Also, the extended MELPA package universe. This and (use-package) allowing me not to worry about installing hundreds of packages really transformed Emacs into a productivity behemoth.
Earlier quoted context omitted.
I don't use customize either, but there are very few things^1 that will be put in it without you explicitly customizing the variable and choosing to save it. So rather than typing elisp code out by hand, you can use the more user-friendly interface to set a variable. If you're -- for example -- version controlling your init file and you use customize, you want to have your customize block version controlled. [1] The…
Customize.el is not only about saving on keystrokes from elisp code, but it is highly discoverable, and importantly, type safe. If you need to put some wacky cons shenanigans to define your font locking rules or whatever, all that is taken care of you in customize. I don't put the output customize.el under version control since I vary my settings somewhat from machine to machine, and I use version control to sync my…
My favorite thing I wish they'd told me about emacs: M-x shell Run a shell (or shells) inside emacs. Great for long running apps like servers. You can search back through the output using normal Emacs search commands. For me, one of the killer features of Emacs. Rename the shell buffer to something else to start another shell.
My favorite thing I wish they'd told me about emacs: M-x shell Run a shell (or shells) inside emacs. Great for long running apps like servers. You can search back through the output using normal Emacs search commands. For me, one of the killer features of Emacs. Rename the shell buffer to something else to start another shell.
Emacs is nice. But it's also a fractal of bad usability design. :/
My favorite thing I wish they'd told me about emacs: M-x shell Run a shell (or shells) inside emacs. Great for long running apps like servers. You can search back through the output using normal Emacs search commands. For me, one of the killer features of Emacs. Rename the shell buffer to something else to start another shell.
My favorite thing I wish they'd told me about emacs: M-x shell Run a shell (or shells) inside emacs. Great for long running apps like servers. You can search back through the output using normal Emacs search commands. For me, one of the killer features of Emacs. Rename the shell buffer to something else to start another shell.
My favorite thing I wish they'd told me about emacs: M-x shell Run a shell (or shells) inside emacs. Great for long running apps like servers. You can search back through the output using normal Emacs search commands. For me, one of the killer features of Emacs. Rename the shell buffer to something else to start another shell.
Both of those other modes have better support for curses applications and act closer to an actual terminal emulator than M-x shell does.
Also, if you like term, you can use the "multi-term" script (http://www.emacswiki.org/emacs/multi-term.el), which will automatically open a new terminal window with M-x multi-term, and you can cycle through your open terminals with M-x multi-term-next and multi-term-prev
Emacs is nice. But it's also a fractal of bad usability design. :/
I honestly think the defaults were made bad on purpose to force people to learn how to configure it.
http://www.forbes.com/sites/carminegallo/2012/06/14/why-the-...
If you'd like a whole book on this topic, I can't recommend Mickey Petersen's "Mastering Emacs" enough: https://www.masteringemacs.org/