Skip to main content

Vim 7: Lovin' It

I finally installed Vim 7. I also took the time to install various plugins. Here are some things that are making me happy:
  • Honest to goodness, real tabs.
  • Auto-completion and built-in documentation lookup for many different programming languages.
  • Editing files and browsing directories remotely over scp works.
  • Subversion integration via the vcscommand plugin is helpful.
  • Vim is still charityware which makes me proud to use it.
Vim is still my favorite editor because I truly believe that its style of keybindings is faster for experts. Furthermore, it has one of the strongest and most flexible syntax highlighting systems:
  • It supports a ton of languages by default.
  • It does well with files that mix languages like HTML, CSS, and JavaScript.
  • It doesn't get confused by Python strings such as """He said, "hi"!""" ;)
I code in a lot of languages, and I love that Vim is consistent and helpful.

Comments

Anonymous said…
Hi jj,
Congrats on the launch.

Any more info on Vim? What plugins are you using? I'm learning python and returning to vi(m) after a long absence. It would be great if there was a plugin that could 'auto' fold.

My eyes are telling me to buy a hardcopy version of a vim manual. I wonder if there are any plans to update it, or can you point to any good sources of info?
Cheers, John
CARFIELD said…
I only use the basic vi function from VIM and don't know anything that you've talk about...

Would you point me some link/blog that teach people using these features?
jjinux said…
I've created a new post to respond to these two comments.

Popular posts from this blog

Drawing Sierpinski's Triangle in Minecraft Using Python

In his keynote at PyCon, Eben Upton, the Executive Director of the Rasberry Pi Foundation, mentioned that not only has Minecraft been ported to the Rasberry Pi, but you can even control it with Python. Since four of my kids are avid Minecraft fans, I figured this might be a good time to teach them to program using Python. So I started yesterday with the goal of programming something cool for Minecraft and then showing it off at the San Francisco Python Meetup in the evening.

The first problem that I faced was that I didn't have a Rasberry Pi. You can't hack Minecraft by just installing the Minecraft client. Speaking of which, I didn't have the Minecraft client installed either ;) My kids always play it on their Nexus 7s. I found an open source Minecraft server called Bukkit that "provides the means to extend the popular Minecraft multiplayer server." Then I found a plugin called RaspberryJuice that implements a subset of the Minecraft Pi modding API for Bukkit s…

Apple: iPad and Emacs

Someone asked my boss's buddy Art Medlar if he was going to buy an iPad. He said, "I figure as soon as it runs Emacs, that will be the sign to buy." I think he was just trying to be funny, but his statement is actually fairly profound.

It's well known that submitting iPhone and iPad applications for sale on Apple's store is a huge pain--even if they're free and open source. Apple is acting as a gatekeeper for what is and isn't allowed on your device. I heard that Apple would never allow a scripting language to be installed on your iPad because it would allow end users to run code that they hadn't verified. (I don't have a reference for this, but if you do, please post it below.) Emacs is mostly written in Emacs Lisp. Per Apple's policy, I don't think it'll ever be possible to run Emacs on the iPad.

Emacs was written by Richard Stallman, and it practically defines the Free Software movement (in a manner of speaking at least). Stal…

JavaScript: Porting from react-css-modules to babel-plugin-react-css-modules (with Less)

I recently found a bug in react-css-modules that prevented me from upgrading react-mobx which prevented us from upgrading to React 16. Then, I found out that react-css-modules is "no longer actively maintained". Hence, whether I wanted to or not, I was kind of forced into moving from react-css-modules to babel-plugin-react-css-modules. Doing the port is mostly straightforward. Once I switched libraries, the rest of the port was basically:
Get ESLint to pass now that react-css-modules is no longer available.Get babel-plugin-react-css-modules working with Less.Get my Karma tests to at least build.Get the Karma tests to pass.Test things thoroughly.Fight off merge conflicts from the rest of engineering every 10 minutes ;) There were a few things that resulted in difficult code changes. That's what the rest of this blog post is about. I don't think you can fix all of these things ahead of time. Just read through them and keep them in mind as you follow the approach above.…