21–30 of 71 posts
> "As always, if you encounter problems building or using Emacs, please send a report to address@hidden with full details" What's up with "address@hidden"?
It also populates all the information useful for devs.
The reporting address seems to be bug-gnu-emacs at gnu.org
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.
But for Haskell and Clojure development, it's hard to beat the tight integration features that Emacs provides (e.g. quickly piping your code or a single function to the REPL for testing). Vim is not designed for this; there are plugins available to approximate it, but it’s a bit hacky and nowhere close to Emacs).
Honestly, it's not hard to learn the basics of both. If you're accustomed to Vim commands, Emacs has `evil-mode`. There's also the slick `god-mode`, which is like Vim's Normal mode for Emacs.
Both tools are great in their own ways. Personally, I regularly use and love them both.
Earlier quoted context omitted.
Hehe because I don't subscribe to monotheism? ;) I prefer vim's modal editing mode and have been using it as my primary for as long as I can remember. For clojure/lisp, I found that the vim tooling was just not as elegant/efficient as emacs (fireside et al arent as nice as cider/swank), and decided to learn how to use it. It's not that much of an "antipattern" because the keymaps are very different. I don't like usin…
You might consider checking out evil mode. It's for real. Does not feel like emulation at all.
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.
Earlier quoted context omitted.
Hehe because I don't subscribe to monotheism? ;) I prefer vim's modal editing mode and have been using it as my primary for as long as I can remember. For clojure/lisp, I found that the vim tooling was just not as elegant/efficient as emacs (fireside et al arent as nice as cider/swank), and decided to learn how to use it. It's not that much of an "antipattern" because the keymaps are very different. I don't like usin…
You might consider checking out evil mode. It's for real. Does not feel like emulation at all.
Earlier quoted context omitted.
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.
I typically use Vim for quick edits on my Mac, and especially on remote boxes. But for Haskell and Clojure development, it's hard to beat the tight integration features that Emacs provides (e.g. quickly piping your code or a single function to the REPL for testing). Vim is not designed for this; there are plugins available to approximate it, but it’s a bit hacky and nowhere close to Emacs). Honestly, it's not hard to…
I hope some day an editor, written in Haskell, allowing to emulate Vi and and Emacs behaviour will become more appropriate for Haskell programming than any other editor and offer you to either the Vi or Emacs style.
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…
For example "M-x tree undo" show me "undo-tree-visualize (C-x u)".
Now I use Helm all over the place: (recent) file opening (within the current project), buffer switching, grepping, etc. It really changed how I interface Emacs.
Earlier quoted context omitted.
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.
Hehe because I don't subscribe to monotheism? ;) I prefer vim's modal editing mode and have been using it as my primary for as long as I can remember. For clojure/lisp, I found that the vim tooling was just not as elegant/efficient as emacs (fireside et al arent as nice as cider/swank), and decided to learn how to use it. It's not that much of an "antipattern" because the keymaps are very different. I don't like usin…
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…
Have you tried Helm in Emacs? For me it binds to M-x, and I can find a "lost" command by typing just bits. For example "M-x tree undo" show me "undo-tree-visualize (C-x u)". Now I use Helm all over the place: (recent) file opening (within the current project), buffer switching, grepping, etc. It really changed how I interface Emacs.