Live data from Hacker News

Why GNU Emacs?

elephly.net

141–150 of 317 posts

Re: Why GNU Emacs?

#141
post #127
post #36

Earlier quoted context omitted.

Helm may be the most flagrant example of a terrible package that remains inexplicably popular. I haven't uninstalled it yet, because there are a few packages that use helm that don't have ido equivalents yet, but I try to minimize my usage of it as much as possible. Issues include: - Significant performance issues - Constant bugs - updates often break the package completely, especially if you're using the melpa versi…

I think both built-in completing read and helm/ivy have their uses. ido is best for when you know what you want and want to get it to it with minimal number of keystrokes. helm seems better for when you want to review many (but not too many) options before deciding on what you want. I find ido unusable for find-file, because of how it splits up directory from filename. So I use the builtin completion. But I rarely op…

I love ido's find-file, but I think that's because I've made it behave much differently than the defaults. The ability to use backspace to go up one full directory, jump to home with ~/ at any point, jump to / with // at any point, and navigate folders quickly with fuzzy matching and RET is really, really nice.

To be fair, most of my file opening is done with projectile, which, when you exclude the right files and use ido, works fantastically well. I can get to nearly anything I've been working on in two commands - projectile-switch-to-project (C-c p p) and projectile-find-file (C-c p f).

I'm not sure what you mean by "how it splits up directory from filename" - could you clarify?

ido-use-virtual-buffers is indeed awesome - I really love it.

Re: Why GNU Emacs?

#142
...Click a button, or invoke a command and an empty, unremarkable rectangle appears. Little you know that it is a relic from an age long past...

Emacs to me, first and foremost, is a doorway to another dimension, a place you can escape to from the absolute drudgery of the contemporary software development.

...A relic, yes, but it seems as alive as ever, a dark block inside it, blinking, like a pulse on a medical instrument...

It is also a glimpse into what professional tools might be like, if they were not so obsessed about beginner users. [1]

...You wonder what the hell you should do with it...

[1] I think Erik Naggum kind of nailed it in http://www.xach.com/naggum/articles/3065048088243385@naggum....

Re: Why GNU Emacs?

#143

Earlier quoted context omitted.

I tried this, but found that the issue is that most major modes use a "grammar" that make sense to native-emacs user, and ended up fighting with them.

After a day of editing on Emacs on a MacBook Pro, my hands felt like they were going to shrink and stick into a contorted state. So I tried Evil which does work fairly well for editing text. In some ways it's better than Vim--the :substitute is really nice as it shows all pending substitutions in the buffer. But as you said, some major modes work with Evil and others don't, so I'm never sure what I'm going to get. Ir…

Reconfiguring OS X to substitute control for caps lock really helped me. Yes, many keyboards had them swapped physically some time ago. Here's an example of a keyboard from a Sun workstation:

http://xahlee.info/kbd/i/kb/sun_keyboard_left.jpg

Re: Why GNU Emacs?

#144
post #130

I try Emacs around once per year. The problem is it's so slow under OSX. It's much faster on my 2007 iMac running Linux than 2013 mbp. I even tried to run it under X-Quartz but still performed poorly. What can I do?

Turn up the limit on garbage collection made a big difference for me. I'll post my .emacs.d on github and reply here.

I'd only make a personal recommendation for emacs if you were doing Clojure development. Emacs+Cider+clj-refactor puts everything else to shame.

Otherwise I'd just say use atom or sublime or whatever ide.

Re: Why GNU Emacs?

#145
Out of curiosity, I have tried Vi and Emacs, but the CLI text editor I have gone back to is GNU nano.

Am I missing something?

Re: Why GNU Emacs?

#146
post #25

Emacs is a fine editor to use until you write your own. It's the only way to make your primary interactive tool work exactly the way that you think it should.

That's a hefty endeavor. Care to share more about your experience writing your own?

I think pklausler means that, out of the box, emacs is decent but, over time, you slowly mold it into something that is more truly yours.

That's been my nearly twenty year experience with emacs.

Re: Why GNU Emacs?

#147
post #145

Out of curiosity, I have tried Vi and Emacs, but the CLI text editor I have gone back to is GNU nano. Am I missing something?

You are missing some things, yes. A more capable editor is well worth some time invested.

I'd recommend learning whichever of vi and emacs is better represented amongst those you can easily go to for guidance.

If you choose vi, I also recommend http://vim-adventures.com/ - I have only played through the free bit, but if the quality is consistent I expect it's worth paying for if you want to learn vim and have a bit of fun while you're at it.

Re: Why GNU Emacs?

#149
post #125

Does anyone have an opinion on Spacemacs [0]? I haven't used it, nor Vim/Emacs. Just came across it during researching the two. Spacemacs appears to have excellent documentation though. [0] http://spacemacs.org/

I switched from vim to spacemacs a few weeks ago and I don't regret it. The fact that you can run a shell in a buffer, have on the fly syntax checking and so on makes coding much more comfortable and you feel like you're using a full blown ide instead of just a text editor. Would recommend

Re: Why GNU Emacs?

#150
post #128

Earlier quoted context omitted.

I would instantly disregard anyone who says this. Just run it in daemon mode and connect with emacsclient.

why is that not the default behavior then?

Because it would take up memory from everyone, including non-emacs users.
Post reply on HN