Skip to main content

Handy vim - easily generate properly formated bullet lists

This is a problem I run into fairly often, because I do a bit of hand-coding HTML from word files or other content that clients send me. When you cut and paste the items for a bullet list into an html document, they often come in one per line with no formatting (or sometimes they have a "*" at the start of each line.

Obviously you can create a macro to automate the process of putting <li> tags around each item, but there's an even faster way to do this using vi's powerful regular expression tools.

Of course, this will only be useful if you can use vi, a command-line text-editor. If you're on shared hosting or something, you may be out of luck. There is a windows version of vi, but I haven't really done more than mess with it a bit. If you're on OSX, you're probably in luck - you can use the console, and I think that it has vim installed, although it's been like eight years since I used OSX regularly.

First, figure out the lines that you want to change - you need to know the first and last line to apply the expression to. For example, let's stay they're lines 5-10 of the code.

Then apply the following regular expression by pressing ":" and then typing it in:
5,10 s/\(.*\)/\t<li>\1<\/li>/

The basic pattern here is s/pattern/replacement/. So, to break it apart sequentially:

5,10 - apply the pattern only to lines 5-10
s - subsitute
/\(.*\)/ - match this pattern - .* means all characters, the escaped parentheses around it tell vi to remember what was matched for use in the replacement
\t<li>\1<\/li> - the replacement portion of the pattern, the \1 is a stand-in for what was matched in the matching pattern, the rest of puts a tab and open LI tag in front, with a closing LI tag after.

Of course similar patterns can be used for all sorts of things, such as replacing variable names in code. Enjoy!
Labels:

Comments

Post a Comment

Popular posts from this blog

Another VI tip - using macros, an example

God I love VI. Well, actually, vim but whatever. Here's another reason why. Suppose you need to perform some repetitive task over and over, such as updating the copyright date in the footer of a static website. (Yes, yes I know you could do a javascript thing or whatever, just bear with me.) Of course you could just search and replace in some text editor, changing "2007" to "2008" (if you're stupid) - and you'll end up with a bunch of incorrect dates being changed, most likely. What you need to do is only change that date at the bottom. And suppose that because of the formatting, you can't use the "Copy" part of the string in a search replace - perhaps some of the pages use "©", some spell out "Copyright" etc. This is where vi macros come in handy. A macro in vi is exactly what you expect, it records your actions and allows you to play them back. To start recording, press q followed by a character to use to "stor...
6 comments
Read more

Using FIle FIlters in FileZilla

Here's a handy tip for situations when you want to download a large number of files - but only of a certain type. For example, perhaps you want to download all the PHP files from a largish website, scattered through many subdirectories. Perhaps you're making a backup and don't want any image files, etc. FileZilla (still the best FTP in my opinion) has a handy feature called filename filters - located under the Edit menu. Here you can set various filters that filter out files based on their filename. Took me a minute to figure that out - you're saying show only PHP files, rather you're saying filter out files that do not have ".php" as their suffix. For some reason, that seems a little backwards to me, but whatever. It works quite well. You can also check whether the filter applies only to files, only to directories - or both. In this example, you'd want to check only files, as otherwise you won't see any directories unless they happen to end in...
1 comment
Read more

Empty $_POST array in MAMP

OK, so just spent 30 minutes debugging this. I'm now using a mac as my development platform for one of the sites I support. It's worked pretty well until today when I started adding a new feature. I ran into a weird problem where POST arguments were not being made available, either in $_REQUEST or $_POST - while GET arguments were. Thanks to this page , I was pointed in a useful directions. Turns out for some reason my version of MAMP had a max_post_size of "3200M" set in its php.ini file. That was not working too well - when I changed it to 32M, everything went back to working normally. So, perhaps that will help someone else who's driving themselves crazy!
Post a Comment
Read more