Live data from Hacker News

From Vim to Emacs in fourteen days (2015)

blog.aaronbieber.com

171–180 of 182 posts

Re: From Vim to Emacs in fourteen days (2015)

#171
post #52
post #31

Earlier quoted context omitted.

Emacs vs Vim is like comfort food for software-related online discussions.

And it's even more useless fluff than it was back in the day because people used Vim and Emacs in large numbers back then. These days the vast bulk of professional developers use Visual Studio Code. Compared to VSCode vs. IntelliJ, Vim vs. Emacs is a sideshow at best.

[deleted]

Re: From Vim to Emacs in fourteen days (2015)

#172

Am I the only person who uses Lem? An Emacs-clone written and extended in Common Lisp rather than the weird version of Lisp Emacs uses. https://github.com/lem-project/lem

I tried it, but the underlying Roswell system isn't perfect at least.

Simple Make fails on linux out of the box.

And the look&feel and features are very far from emacs.

Re: From Vim to Emacs in fourteen days (2015)

#173
post #94
post #51

Earlier quoted context omitted.

I know org.mode is a deep rabbit hole - but do you have an example of "dynamic code blocks in documents"? I've recently switched my "notes.txt" buffer in (neo)vim to markdown ("notes.md) - along with a slightly more magical syntax plug-in - and I'm pleasantly surprised by the quality of life improvements from having multiple code/script snippets highlighted in-line (eg: ```SQL (... Snippet...) ``` in a paragraph foll…

I made a video[0] showing off the power of org-babel, which is the part of org that lets you embed dynamic code blocks in your document. In the video I write a little essay[1] on how git stores data that has a lot of dynamic content that is managed by org. It's a bit like reproducible research or literate programming, but for me it's all about writing technical documents that are easy to keep consistent when things c…

Thanks for this video, this is the one I link to when asked for a Babel demo.

Re: From Vim to Emacs in fourteen days (2015)

#174
post #80

Earlier quoted context omitted.

Take for example, incremental search. Emacs has it by default. Vi being older didn't have it, but vim has it. It has to be turned on. Then it doesn't work as well as emacs. In emacs you can type to search then ctrl+s to move to next match then continue to type to edit the search string, and so on. This is just one example. Replace has advantages in emacs when it comes to case matching. And it goes on and on.

Incremental search needs to be enabled, yes, but it’s just one line in your .vimrc. What do you mean by “type to search”? Sounds like you’re omitting the “start search” key combo. Your example in Vim: * / to start a forward search * type in the word and hit enter * n/N for next/previous match To modify the search: * q/ opens your search history with the cursor at the last searched string * modify the search string us…

Thank you for that note on q/ ... I knew about q: for command history, and was wondering if there was an equivalent for search history.

Re: From Vim to Emacs in fourteen days (2015)

#175
post #142

Tangentially related: I've used emacs for coding for a decade, and for email for a few years. I love it. But I'm missing out on its arguably strongest feature: elisp! My config file is a tragedy of stuff I hamfistedly cobbled together. I'd like to learn this skill properly, and thus conquer the world (I assume this makes me able to). Can anyone recommend a resource? I speak some C-like languages, and Python and Haske…

More replies than you can shake a stick at here.

https://emacs.stackexchange.com/questions/47318/how-can-i-st...

(I've been cluelessly hacking at emacs for decades, and there's ALWAYS something new to learn.)

Re: From Vim to Emacs in fourteen days (2015)

#176
post #142

Tangentially related: I've used emacs for coding for a decade, and for email for a few years. I love it. But I'm missing out on its arguably strongest feature: elisp! My config file is a tragedy of stuff I hamfistedly cobbled together. I'd like to learn this skill properly, and thus conquer the world (I assume this makes me able to). Can anyone recommend a resource? I speak some C-like languages, and Python and Haske…

https://www.emacswiki.org/emacs/LearnEmacsLisp looks pretty good, too, actually.

Re: From Vim to Emacs in fourteen days (2015)

#177
post #13

I started with emacs and never learned vim. What am I missing?

Primarily the fact that vim is EVERYWHERE and starts up instantly with zero config, so it's great when you find yourself on J. Random Server and need to edit something. It's good to know some basic basics.

Re: From Vim to Emacs in fourteen days (2015)

#178
post #175
post #142

Tangentially related: I've used emacs for coding for a decade, and for email for a few years. I love it. But I'm missing out on its arguably strongest feature: elisp! My config file is a tragedy of stuff I hamfistedly cobbled together. I'd like to learn this skill properly, and thus conquer the world (I assume this makes me able to). Can anyone recommend a resource? I speak some C-like languages, and Python and Haske…

More replies than you can shake a stick at here. https://emacs.stackexchange.com/questions/47318/how-can-i-st... (I've been cluelessly hacking at emacs for decades, and there's ALWAYS something new to learn.)

Thanks!

Re: From Vim to Emacs in fourteen days (2015)

#179
post #123

Earlier quoted context omitted.

I've been using Spacemacs for Clojure development for years but stable has been stuck on the same version for ages so is it actually maintained?

You should switch to develop. They are working on release 300 and there are commits being merged daily.

It's been thaty way for years so not very encouraging. With develop I can't just click Update Packages. Any advantages these days of staying with Spacemacs over Doom?

Re: From Vim to Emacs in fourteen days (2015)

#180
Here we go again. Vim vs. Emacs. A decades-old argument that actually doesn't have any merits.

Because Vim and Emacs are two distinct categories. The only thing that makes them similar is that they are both based on something. That something is an idea. And not just an ordinary, everyday concept, but an influential, holy grail type of thing.

Vi and the concept of the modality is an incredible, powerful, fantastic model. People who never hardheartedly tried to learn Vi-model just don't get to say anything about it. Can you respect an opinion about CRISPR coming from someone who has no clue about polynucleotide chains and DNA?

Yes, Vim is not overly intuitive for a complete beginner. Like many, perhaps most awesome tools, it too has a certain level of sophistication. You cannot enter the Suez or Panama Canal gates' control room and suggest removing all those knobs, switches, buttons, etc., and instead, install one colossal touch screen because that would be "a much more intuitive interface".

Vim is hard to learn, but you see, there's usually a strong correlation between something that's not so easy to acquire and simplicity gained later. Conversely, things that are easy to pick up, very often later become cumbersome and annoyingly counter-productive. Rich Hickey's "Simple Made Easy" rhetoric very nicely manifests that.

So yes, Vi-model is an incredible idea. Vim, Neovim, Evil, etc., are just implementations of that idea.

Now, Emacs is based on another mind-blowing idea. The idea of practical notation for lambda calculus, what is known as Lisp. Lisp, probably can be crowned as the most important idea in computer science. It's just hard to think of something more influential than Lisp. Emacs is just a practical implementation (and frankly, not the best one) of that idea.

Arguing what's better - Emacs or Vim is like debating what was more important in the history of health care - the invention of anesthesia or discovery of penicillin.

Both Vim and Emacs are awesome, and one is not better than another. If you can't see that - then probably there's a big hole in your understanding of at least one of the ideas they are based on.

Post reply on HN