41–50 of 71 posts
As someone who uses emacs purely for clojure/lisp and vim for everything else, the biggest feature for me is the fact that this will be the first version of emacs to support menus in terminal mode . So for all the commands you don't remember, a menu is now a click or F10 away. To quote, "Emacs now supports menus on text-mode terminals. If the terminal supports a mouse, clicking on the menu bar, or on sensitive portio…
Earlier quoted context omitted.
If you are a Unix user, you almost need to know enough vi to edit a simple file. crontab -e is considered a minor sin in the Church of Emacs, but only a minor one. ESC:q!
export EDITOR=emacs Then crontab -e will start emacs instead of vi.
I know enough vi to open a file, move up, down, left, and right, search, delete and insert text. And I often run afoul of my emacs muscle memory just doing that. But you really need to know the vi basics if you admin unix machines.
As someone who uses emacs purely for clojure/lisp and vim for everything else, the biggest feature for me is the fact that this will be the first version of emacs to support menus in terminal mode . So for all the commands you don't remember, a menu is now a click or F10 away. To quote, "Emacs now supports menus on text-mode terminals. If the terminal supports a mouse, clicking on the menu bar, or on sensitive portio…
Just curious. How did you manage to use both emacs and vim? I've seen that people accustomed to one editor are usually averse to using the other.
It worked out pretty well as long as I used Emacs in an X window and vi on the command line. But if I ran emacs in a terminal, I automatically started typing vi commands into it.
Earlier quoted context omitted.
export EDITOR=emacs Then crontab -e will start emacs instead of vi.
If emacs is installed. It often isn't. vi almost always is. I know enough vi to open a file, move up, down, left, and right, search, delete and insert text. And I often run afoul of my emacs muscle memory just doing that. But you really need to know the vi basics if you admin unix machines.
Of course I realize that this is mostly me being silly, but it’s also rather educational.
As someone who uses emacs purely for clojure/lisp and vim for everything else, the biggest feature for me is the fact that this will be the first version of emacs to support menus in terminal mode . So for all the commands you don't remember, a menu is now a click or F10 away. To quote, "Emacs now supports menus on text-mode terminals. If the terminal supports a mouse, clicking on the menu bar, or on sensitive portio…
Just curious. How did you manage to use both emacs and vim? I've seen that people accustomed to one editor are usually averse to using the other.
However, I still use Emacs for LaTeX documents via AUCTeX, because I find it far more powerful for basic editing, with commands to insert directives, environments, \item, etc.
Earlier quoted context omitted.
Slime is really amazing. It provides tons of features of which here are a few (these work with Common Lisp, I have no clue if they work with Clojure). Inspector[0]: You can click on objects to "inspect" their values. This includes hash-tables, arrays, and closures. In addition you can execute arbitrary code on these objects at any time, even while a program is running. Trace Dialog[1]: Most Lisp implementations alrea…
That actually sounds a lot like Smalltalk.
Earlier quoted context omitted.
If you are a Unix user, you almost need to know enough vi to edit a simple file. crontab -e is considered a minor sin in the Church of Emacs, but only a minor one. ESC:q!
export EDITOR=emacs Then crontab -e will start emacs instead of vi.
export ALTERNATE_EDITOR=emacs EDITOR=emacsclient VISUAL=emacsclient
This way, crontab -e should open a new Emacs frame (or start Emacs, if it isn't already running). It will speed things up and make the experience better, while giving you access to all the things you're working on in an already running Emacs.
See also: http://www.emacswiki.org/EmacsClient.
Earlier quoted context omitted.
As a dev who's always used Sublime/Atom and sometimes Vim, what's the benefit of Emacs for Lisp?
Slime is really amazing. It provides tons of features of which here are a few (these work with Common Lisp, I have no clue if they work with Clojure). Inspector[0]: You can click on objects to "inspect" their values. This includes hash-tables, arrays, and closures. In addition you can execute arbitrary code on these objects at any time, even while a program is running. Trace Dialog[1]: Most Lisp implementations alrea…
I recommend those who are not familiar with conditions/restarts to read up a bit on them. This is something like exception handling, but an order of magnitude more powerful.
As someone who uses emacs purely for clojure/lisp and vim for everything else, the biggest feature for me is the fact that this will be the first version of emacs to support menus in terminal mode . So for all the commands you don't remember, a menu is now a click or F10 away. To quote, "Emacs now supports menus on text-mode terminals. If the terminal supports a mouse, clicking on the menu bar, or on sensitive portio…
As a dev who's always used Sublime/Atom and sometimes Vim, what's the benefit of Emacs for Lisp?