2718.us blog » macvim

Two Days with Xcode Made Me Miss MacVim

2718.us — Tue, 28 Apr 2009 15:14:10 +0000

I spent a large chunk of 2 days bashing out some code for asLJ, which is in a mix of Applescript Studio and Objective-C all pieced together with its GUI in Xcode. While I don’t dislike Xcode’s text editor—in fact, I have had moments where I really liked it and wondered about using it for everything—I discovered that the past few months with MacVim/gVim/Vim have gotten me much more into the power of Vim. Moving around through the code felt slow. Systematic changes were annoying (simple find-replace isn’t so bad, if not as quick to do as in Vim, but changing “[thing1],[thing2],” to “[thing2],[thing1],” for various values of thing1 and thing2 on numerous lines was a bunch of mouse-keyboard-mixed hackery instead of a single well-constructed command.

There aren’t a whole lot of little details like that for me to point to and say “see? Vim is better!” Ultimately, what it comes down to is that I am eager to have to do something like PHP programming or web site maintenance for which I’ll use Vim.

Improving Your Vim-Fu

2718.us — Thu, 26 Feb 2009 01:18:43 +0000

Efficient Editing With vim

This tutorial assumes a basic knowledge of vim — insert mode, command mode, loading and saving files, etc. It is intended to help vi novices develop their skills so that they can use vi efficiently.

(Posted mostly for my own reference, though I thought it might be of use to anyone else who wants to improve their use of vim.)

Text Editors

2718.us — Wed, 12 Nov 2008 20:44:32 +0000

When I was first learning structured programming, I used an IDE (TurboPascal). Since then, I have rarely used an IDE outside of specialized language development environments like VisualBASIC. Mostly, I use a text editor that I link up with a good sftp program to edit remotely or that I use in conjunction with subversion. For a long time, when I was still programming heavily on PCs, I used TextPad. It’s probably still toward the top of my list, but it’s been so long since I used a PC as one of my primary machines that it’s hard for me to know.

The lack of TextPad for mac has left me searching, on and off, almost constantly for the “right” mac text editor. Most of the time now, that search leaves me right back at Komodo Edit, the free cross-platform text editor built on Gecko and Scintilla that I’ve been using for a logn time now. Every other major editor just seems to be missing something I’ve come to really like in Komodo Edit, even as slow and clumsy as the interface can be sometimes.

I really wanted to like BBEdit, TextWranger, TextMate, skEdit, subEthaEdit, Coda, etc., but none of them seemed to have the simplicity of code-completion (including variable and constant name completion) and intelligent code auto-indenting that Komodo Edit does. I wanted to like the integration of various resources in Coda, but having the reference materials in the one program versus in a web browser window over on that second monitor there just didn’t seem to make enough of a difference. I wanted to think that having an editor that could do sftp and subversion was worthwhile, but it just didn’t seem to matter to my workflow.

It’s been so long since I’ve been away from TextPad that I’m not sure even it would compare to Komodo Edit. Of course, the one tool that is poised at any moment to start eating into Komodo Edit’s share of my use time is MacVim (this is apparently a new port of vim). Vi/vim is so unbelievably powerful… and so much more my style than Emacs. Vi has been my text editor of choice at the command line for about a decade or so now. See also Why, oh WHY, do those #?@! nutheads use vi? and the two graphics below.