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

Editors (Vim)

missing.csail.mit.edu

Post reply on HN
Print view View original

31–40 of 120 posts

Re: Editors (Vim)

#31

Post by fstarship »

satvikpendem wrote: post #19
jedwards1211 wrote: post #2

Vim emulation in VSCode worse than any other IDE I've used. All extensions have to run on the same thread in a background process and intercepted keystrokes are passed to that process over IPC. So if other extensions (like the TS language tools) are tying up the extension host process, the Vim extension can't respond to your keyboard input until other extensions yield. Performance issues come and go but for awhile I…

https://marketplace.visualstudio.com/items?itemName=asvetlia... This is using a real neovim instance rather than emulation, and performance is excellent for me.

I second that and would like to point out that apt-get only saves an old copy of neovim. I had to install the latest version using snap.

This issue is described in the link but I thought it deserves highlighting

Re: Editors (Vim)

#32

Post by mongol »

partiallypro wrote: post #29

I'm by no means a high level expert of command line, but if I need to do a quick edit I just use nano, and if I need to get down and dirty I use VS Code. Is this abnormal? I know a lot of power users use Vim, but I've just never fallen in love with it.

It is not abnormal. I used to use pico as my terminal editor and nedit as X editor the first five years or so I used Linux / Unix. Today I use VSCode as well, but vi rather than pico (nano). Over the course of many years I got more and more comfortable with it. It was never really a conscious choice. But it is always there. Perhaps it was the times I needed to fix things when booting in emergency mode that forced me to learn vim enough to get by, and eventually proficient.

Re: Editors (Vim)

#33

Post by pixelmonkey »

I've been a happy vim user for many years, over a decade. But I was shocked at how this talk, published on YouTube in 2018 from a recorded lecture by an engineer at Yelp named Leeren Chang, basically made vim’s internal model “click” for me and made vim even more fun to use. I really feel the presenter did such a great job showcasing vim ideas — conceptually, visually, and by direct example — that, by the end, I downloaded the talk into my “great tech talks” stash and labeled it, “vim’s missing manual.”

Here it is: https://youtu.be/E-ZbrtoSuzw

Re: Editors (Vim)

#34

Post by jchook »

adamredwoods wrote: post #13

I respect Vim, I've seen it used with impressive speed, BUT I am so used to command-s to save, that I don't feel ready to :w enter all the time. VS Code is powerful, and learning the keyboard shortcuts for that are getting better every day (command-shift-p format-selection enter).

You get over it fast.

1. You can bind save to any key combo you want. I personally use w. I find it more ergonomic, fast, and portable than command-s.

2. Every action in vim reads like a little story. You start to speak the stories to yourself. For example:

Select the entire line (V), move to the end of the line ($), move to the matching end brace (%), delete (d)

3. Then you realize you can store those stories into a macro and execute them ad hoc, and the world becomes amazing.

The things you learn are cumulative. You begin to expect the pattern to continue and more often than not it does.

Re: Editors (Vim)

#35

Post by gorgoiler »

blt wrote: post #25
gorgoiler wrote: post #14

I’m so used to vim as a code editor that I assumed, after the introduction, this article was going to be castigating me for trying to write prose in vim (which I indeed try to do on a regular basis, with what feels like a lot of friction.) Perhaps, as they imply, I should dust off a copy of Microsoft Word and switch back to that!

There is no conflict if you use LaTeX :)

Goyo.vim was pretty helpful. So was formatoptions +a.

(The typesetting part isn’t the issue. Concentration and ease of flow in the editor feel hard in vim, and LaTeX wouldn’t fix that.)

Re: Editors (Vim)

#36

Post by muststopmyths »

gorgoiler wrote: post #14

I’m so used to vim as a code editor that I assumed, after the introduction, this article was going to be castigating me for trying to write prose in vim (which I indeed try to do on a regular basis, with what feels like a lot of friction.) Perhaps, as they imply, I should dust off a copy of Microsoft Word and switch back to that!

complete the circle and use a vi plugin for Word http://www.viemu.com/

Re: Editors (Vim)

#37

Post by EduardoBautista »

oehtXRwMkIs wrote: post #12
chongli wrote: post #7

Earlier quoted context omitted.

As a long time vim user, I’ve tried VSCode a few times and I cannot for the life of me figure out what all the hype is about. Can anyone who is proficient with it explain the philosophy behind it and what makes it so great? This is a sincere question, not a rhetorical one.

It's very featureful and very easy to pick up. So I speculate that most of its popularity is with people that unfortunately have not yet been enlightened by vim/emacs.

I used Vim for several years before switching to Sublime Text 3.0 and now VS Code. VS Code support for TypeScript is just unmatched on any other editor.

Re: Editors (Vim)

#38

Post by pvg »

chongli wrote: post #7
jedwards1211 wrote: post #2

Vim emulation in VSCode worse than any other IDE I've used. All extensions have to run on the same thread in a background process and intercepted keystrokes are passed to that process over IPC. So if other extensions (like the TS language tools) are tying up the extension host process, the Vim extension can't respond to your keyboard input until other extensions yield. Performance issues come and go but for awhile I…

As a long time vim user, I’ve tried VSCode a few times and I cannot for the life of me figure out what all the hype is about. Can anyone who is proficient with it explain the philosophy behind it and what makes it so great? This is a sincere question, not a rhetorical one.

It's Emacs for Javascript people - a good thing since Emacs is moribund and most programmers are at least a little bit Javascript people. A highly programmable, cross-platform editor with zillions of extensions/modes that support all sorts of languages and environments. People complain about its resource requirements and performance, just like they did with Emacs. Vi(m) users are the natural enemy of VSCode, just like they were the natural enemy of Emacs, continuing their long proud tradition of being wrong about everything. I think that's roughly where it fits 'philosophically'.

Re: Editors (Vim)

#39

Post by ulisesrmzroche »

The best part about vim is modal editing and the key-command interface. Other than that, it’s pretty much the same as everything else, worse, cus vimscript is an abomination.

Best setup is vscode with vim emulation and I’ve been using vim profesionally almost 15 years now.

Funny enough, I actually liked writing prose with Vim but I’m using Ulysses as an editor for writing prose now

Post reply on HN