Skip to main content

Vim: Best Vim Article Ever

Why, oh WHY, do those #?@! nutheads use vi?

Comments

Robert said…
Don't take this the wrong way, but wow! "You are always in normal mode, and only enter insert mode for short bursts of typing text, after which you press Esc".

Ah, isn't it meant to be an *editor*, you know for... editing :-)
jjinux said…
He's right. Insert mode is only for adding new text. Command mode is for moving around, deleting, shifting, reformatting, copy-pasting, etc. Hence, I default to command mode.
Robert said…
Yeah, I know (I did use vim for a while, but it just didn't 'fit my brain').

It just seems so wrong to have a a text editor that has one mode for *inserting text* and another for *everything else that you do when editing text*.

PS to make it explicit - this is meant to be taken tongue-in-cheek!

PPS Blogger is gaining some intelligence - the word verification for this comment included 'jj' :-)
jjinux said…
> PS to make it explicit - this is meant to be taken tongue-in-cheek!

I can't tell how far though ;)

Vim is hard to use. It's hard to learn. I wouldn't even recommend it for new programmers. For them, TextMate is a better option.

However, for people like you and I that have been coding for years, the investment pays off. When I'm refactoring and reformatting code, I can move it crazy fast.
GS said…
It just seems so wrong to have a a text editor that has one mode for *inserting text* and another for *everything else that you do when editing text*.

Actually, in most graphical text editors and word processors you enter 'command mode' too, it's just 'less visible' than in the likes of vim. What happens when you press Alt in MS Word is that the menu gets focus and when you then press 'F', you open the 'File' sun-menu, instead of entering the 'F' in the document. It's the same principle, only less visible in a mouse-driven GUI work.
Robert said…
>> PS to make it explicit - this is meant to be taken tongue-in-cheek!

>I can't tell how far though ;)

Sorry - a bad, late night attempt at some amusement.

> However, for people like you and I that have been coding for years, the investment pays off. When I'm refactoring and reformatting code, I can move it crazy fast.

That's the main reason I spent a fair amount of time using it, but to no avail, I didn't get the big speed improvement others did. I guess the neural pathways in my brain could not be re-programmed - probably too many years using brief, SlickEdit, and dare I say the 'e' word :-)
jjinux said…
> Actually, in most graphical text editors and word processors you enter 'command mode' too...less visible...

Interesting point. I actually really like menus in that it's really easy to discover new things in them. That's why I use gvim. As shocking as this might sound, I don't actually have *every* Vim command memorized ;) Hence, I sometimes refer to the menus. I don't think Vim in command mode is quite as friendly. You really do have to just "know" what key to hit.
jjinux said…
> probably too many years using brief, SlickEdit, and dare I say the 'e' word :-)

What are you using now and what are some of the must have features you find yourself using?
Mark said…
I started learning vim 1 month ago, (December is a slower month, so I can pickup something I always ignores), now I would consider vim as my default editor. I am still in the big learning curve.

Basically I use vim with cscope, gcc, cvs, make etc, the brilliant unix tools. cscope is most import for vim because it provide the way to nevigate code. is there any built in mode in vim that I can browse files in directory, such as ctrl-d in emacs?

I vote the following article from the vim user.

http://www.moolenaar.net/habits.html
jjinux said…
> is there any built in mode in vim that I can browse files in directory

Try ":e ." (i.e. editing the current directory).

> http://www.moolenaar.net/habits.html

I agree. I saw him give that talk at Google :-D
Mark said…
> Try ":e ." (i.e. editing the current directory).

Yes. That give the directory content.
with '-' I can go to the parent directory, and hit enter on a file it will open the file in vim. Interest. Thanks.
B. said…
Of course, I think its also a matter of make-up. As someone reminded me, via this link: Vi users are Ninjas, Emacs users are Pirates. :%s/Ninjas/Awesome/
jjinux said…
That's pretty funny ;)
Mir Nazim said…
@mark
> is there any built in mode in vim that I can browse files in directory

Try NERDTree - http://www.vim.org/scripts/script.php?script_id=1658
Its super awesome and I am sure you will love it.

vim forever!!!
jjinux said…
Dude, that is DOPE, yo!

Rock on!

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p