Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A CEO's Guide to Emacs (2015)

blog.fugue.co

Post reply on HN
Print view View original

131–140 of 180 posts

Re: A CEO's Guide to Emacs (2015)

#131

Post by jeremiep »

ams6110 wrote: post #29
bitexploder wrote: post #17

It is difficult to even describe a productive hand tuned to fit the individual Emails setup compared to standard. Here are some of my favorite Emacs things: Helm + Projectile. Helm will fuzzy complete almost anything in Emacs. Projectile is project management. Together get to any Git repo and file there in very quick. Helm is an option to compare to IDO. I rarely use IDO due to Helm. Magit, widely regarded as a good…

Magit is the only thing that allows me to make enough sense of git to use it.

I've been using Emacs for years but only started using Magit this year, what a fantastic Git client.

It makes everything trivial to do, even rebases become safe and friendly. Its definitely a git client on a league of its own.

Re: A CEO's Guide to Emacs (2015)

#132

Post by nanomoose »

yellowapple wrote: post #128
geokon wrote: post #70

I only really enjoyed Emacs once I learned some ELisp (I think I had tried is 2 or 3 times before that). Honestly I find these guides pretty useless b/c you can copy configs and hack together something without really understanding what you're doing but you'll eventually end up extremely frustrated and unable to work around the quirks and conflicts between configurations. I know the people behind Emacs like to think t…

I dunno. Once I took the time to learn the basic keybindings, even before I even knew what .emacs was, I was already pretty impressed with the auto-indent functionality that seemed to work regardless of the language.

It was the lack of basic keybindings that resulted in me never getting going with it. Everytime I wanted to do "trivial thing" I was expected to write a script. Too much yak shaving.

Re: A CEO's Guide to Emacs (2015)

#133

Post by jeremiep »

microtonal wrote: post #75
neutronicus wrote: post #68

Earlier quoted context omitted.

If you think vi does basic text editing better, try Spacemacs! I switched over recently (the emacs pinky was real...) and I've really gotten to like the vim-y experience (although now I get really frustrated when I vim on a server and the search doesn't work like Spacemacs search).

I used Spacemacs for a while, but switched to a custom configuration with evil, general.el, and which-key. Spacemacs was excessively slow and I also often ran into strange bugs.

I did the exact opposite, I got tired of vanilla Emacs and managing my custom configuration. Then I found about Spacemacs and never looked back.

I didn't get any strange bugs or slowdowns, but then I am using the `develop` branch which is going to be the upcoming .3 release. I also have a few dozen layers installed.

I would miss Spacemacs' layers way too much if I reverted to vanilla. Its integration of evil-mode is also fantastic, something I don't want or need to recreate.

Re: A CEO's Guide to Emacs (2015)

#134

Post by muraiki »

bluenose69 wrote: post #93

This is a great article, not least because of the tangential comments (e.g. that impact test of bicycle-style tubing was weirdly fascinating). All that's said about Emacs is true. I loved it for decades. And then my hand started cramping up because of the key chords. So I tried vim, and hated it for a few days, disliked it for a few more, and then started to like it. I'd never go back, now. Vim is certainly not as po…

Check out spacemacs, which is a distribution of emacs that adapts the entire interface to use vim's approach. It's incredible. http://spacemacs.org/

Re: A CEO's Guide to Emacs (2015)

#135

Post by jeremiep »

lettergram wrote: post #124
arkh wrote: post #78

Earlier quoted context omitted.

I love Emacs. But there were no good multimodes 3 years ago. And autocompletion and hints are often a bitch to get working on things which are not C or C++. The moment you start editing files containing more than one language you're pushed to use a dedicated IDE. And then you discover the joy of "good enough". No need to tinker with config files to get the perfect setup: it works good enough to give you a productivit…

I mean, I use autocomplete for work in python, ruby, golang, C/C++, JavaScript, coffeescript, CSS and probably more in enacts. The trick is the setup, but I've only had problems with minor edge cases (like coffeescript 2). Either way I'll spend an hour and use Elisp to fix it. Really nothing I've found is even close to as robust

I've been using spacemacs for nearly 2 years now and autocomplete has mostly always worked right out of the box after installing the corresponding layer. I rarely even need to reboot Emacs.

Re: A CEO's Guide to Emacs (2015)

#136

Post by [deleted] »

nanomoose wrote: post #132
yellowapple wrote: post #128

Earlier quoted context omitted.

I dunno. Once I took the time to learn the basic keybindings, even before I even knew what .emacs was, I was already pretty impressed with the auto-indent functionality that seemed to work regardless of the language.

It was the lack of basic keybindings that resulted in me never getting going with it. Everytime I wanted to do "trivial thing" I was expected to write a script. Too much yak shaving.

[deleted]

Re: A CEO's Guide to Emacs (2015)

#137

Post by jdormit »

jeremiep wrote: post #135
lettergram wrote: post #124

Earlier quoted context omitted.

I mean, I use autocomplete for work in python, ruby, golang, C/C++, JavaScript, coffeescript, CSS and probably more in enacts. The trick is the setup, but I've only had problems with minor edge cases (like coffeescript 2). Either way I'll spend an hour and use Elisp to fix it. Really nothing I've found is even close to as robust

I've been using spacemacs for nearly 2 years now and autocomplete has mostly always worked right out of the box after installing the corresponding layer. I rarely even need to reboot Emacs.

I'm reading this on Spacemacs right now! It's excellent - it removes a lot of the initial configuration investment required to be productive, while letting you customize as deeply as you want if that's necessary. Plus, it has vim keybindings out of the box ;)

Re: A CEO's Guide to Emacs (2015)

#138

Post by emidln »

arkh wrote: post #78
bitexploder wrote: post #17

It is difficult to even describe a productive hand tuned to fit the individual Emails setup compared to standard. Here are some of my favorite Emacs things: Helm + Projectile. Helm will fuzzy complete almost anything in Emacs. Projectile is project management. Together get to any Git repo and file there in very quick. Helm is an option to compare to IDO. I rarely use IDO due to Helm. Magit, widely regarded as a good…

I love Emacs. But there were no good multimodes 3 years ago. And autocompletion and hints are often a bitch to get working on things which are not C or C++. The moment you start editing files containing more than one language you're pushed to use a dedicated IDE. And then you discover the joy of "good enough". No need to tinker with config files to get the perfect setup: it works good enough to give you a productivit…

Really? I installed Spacemacs and everything "just works". Python, Javascript, Clojure, and Ruby only required to add the appropriate layer to my .spacemacs and restart the editor. Autocomplete, jump to definition, find usages, refactoring, documentation lookups and hints, etc. Spacemacs has been equal to or better than IntelliJ, Eclipse, Atom, VisualStudio Code, Kate, or Sublime out of the box.

which-key being integrated everywhere has made discovery the easiest of ANY editor/IDE I've used. Imagine if there was a consistent place where the menu would pop up if you faltered any key combination. If I'm trying to go a git command in Android Studio (InteliJ) and I forget the command, I don't get part way through and see a popup list of contextual actions. I'm left to move my mouse to the right place, click, and then hope to find my git action in the menu I picked.

More common is the unified way that helm makes dealing with files (you can find similar things in Sublime / Atom / Vim distributions using Unite (or whatever they used these days)). Even though the better editors have this, it's not universal and still a differentiating factor for usability and consistency.

Spacemacs integrates Magit by default. Magit is the first version control interface complete enough that doesn't make me immediately nope out into a terminal for proper git commands.

In my primary projects, I need to edit XML, Clojure, YAML, SQL, Java, Makefiles, and Python files. Spacemacs handles syntax highlighting, autocomplete, refactoring, repl connection and evaluation (where available), project management (makefiles and maven support), and documentation lookups.

Re: A CEO's Guide to Emacs (2015)

#139

Post by emidln »

0xFFFE wrote: post #25
eadmund wrote: post #24

Earlier quoted context omitted.

I think Spacemacs (which is an integrated emacs + evil + a whole lot more) is probably the best upgrade path for a vi/vim user. I even got one of the fellows at the office to upgrade from vim using it!

Thanks, but "upgrade"? ;)

I went from a fully decked out vimrc to Spacemacs when I got tired of managing a .vim directory. I had things like Unite integrated everywhere and a generic repl experience via tmux so I had an inferior-mode for anything I wanted (sql, python, clojure, javascript, bash, ruby), even on remote machines (since it was just copy something from a register to a tmux pane, which could be ssh logged into a remote machine with a repl). I had autocompletion and doc lookups for the languages I cared about. Life was pretty good, but it was beginning to get tedious.

I decided to try Spacemacs hoping I might find their vim imitation to be 90% of what I was using in vim, such that I could take advantage of the excellent CIDER mode for Clojure development rather than hacking an analogue in vimscript + a user.clj file. I found Spacemacs to cover everything I had been doing in vim, almost universally better out of the box than I had before.

Re: A CEO's Guide to Emacs (2015)

#140

Post by IncRnd »

arca_vorago wrote: post #61
IncRnd wrote: post #54

Earlier quoted context omitted.

Emacs may need to be renamed to stEmacs, sixteen megs and constantly swapping. It's no longer 8 megs. :(

If you want tiny gnu editor, just use nano. They fixed the file corruption bug right?

I wouldn't know if nano fixed a file corruption bug or not. I use emacs.
Post reply on HN