41–50 of 180 posts
If you write a small pre-processor (simple to do) you can store your emacs configuration file in a markdown file - allowing you to document all the settings neatly. As I was reading this piece I was imagining that is what the author had done, as it is what I did too: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md
Emacs and the Atreus keyboard and xmonad etc. are white elephants.
a 'white elephant' is a useless gift that noone wants. neither point stands in these cases. that said, you don't have to like them.
Earlier quoted context omitted.
Now, Vim. But I would definitely like to give Emacs another try, just for kicks. Do you think emacs with evil is the path with least resistance for a long term Vi/Vim user?
I’ve been a daily vim user for the past 10 or so years and used it casually before that. Anytime I tried to use emacs I missed the modal aspects of vim and my wrists didn’t like the focus around ctrl in emacs. I recently gave spacemacs a try and it’s been my daily editor for the past few months. There is a lot to learn, but spacemacs solves the main pain points I had with off the shelf emacs and I’ve found it to be v…
Seems like lots of people here are sharing their experience with #emacs. I like it a lot, and think that it would be part of the ideal #workingset for me. However, I have never found a nice 'jump-to-definition that worked for most languages I edit on emacs. I tried ggtags, ctags, pygments. I think I had trouble setting all of these up, and they would not work for many languages I was using. I have not found a good re…
It's a preconfigured Emacs configuration (a bit of an overhaul, but not too intrusive if you run it in Emacs or Hybrid mode).
You can just open source files in languages you haven't touched before and the editor will offer to configure itself for that language.
Go to definition works out of the box for more than a dozen languages. :)
Emacs is like Chinese to me, and truthfully to most developers I know. Is there a gentle intro somewhere? Most of what I've seen is just people throwing out package names with no real explanation.
Once you feel comfortable with those, then you can think about adding other stuff on, and can add things one at a time.
I've been using Emacs since 2000 or so, and that's how I started. It's also how I still often use Emacs today; I don't particularly care for IDE-like features, and I don't use a lot of packages. And I'm still quite productive with it because the base stuff Emacs is good at is already pretty darned good!
Earlier quoted context omitted.
I’ve been a daily vim user for the past 10 or so years and used it casually before that. Anytime I tried to use emacs I missed the modal aspects of vim and my wrists didn’t like the focus around ctrl in emacs. I recently gave spacemacs a try and it’s been my daily editor for the past few months. There is a lot to learn, but spacemacs solves the main pain points I had with off the shelf emacs and I’ve found it to be v…
Author of post here. I have no agenda to convert anyone, but mapping caps lock to control is a good move when trying emacs IMO. If you love vi(m), more power to you!
If you write a small pre-processor (simple to do) you can store your emacs configuration file in a markdown file - allowing you to document all the settings neatly. As I was reading this piece I was imagining that is what the author had done, as it is what I did too: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md
Here's one: http://endlessparentheses.com/init-org-Without-org-mode.html
I did not know about ido-mode, it always surprises me how much I can find new stuff in emacs every week!
Earlier quoted context omitted.
a 'white elephant' is a useless gift that noone wants. neither point stands in these cases. that said, you don't have to like them.
That's not the definition that I learned: a white elephant is an unnecessary luxury with limited utility that you can't obtain and maintain unless you're pretty far from being in need. That's what I meant here.
If you write a small pre-processor (simple to do) you can store your emacs configuration file in a markdown file - allowing you to document all the settings neatly. As I was reading this piece I was imagining that is what the author had done, as it is what I did too: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md