A paean to the text editor

Every librarian should get friendly with a text editor—and no, NotePad, WordPad (both on Windows) and TextEdit (Mac) don't count. Neither does Microsoft Word. A good text editor (sometimes called a "source editor" or "programmers' editor") is the Swiss army knife of software. It does a little bit of everything, and a lot of things surprisingly well.

Need to edit an HTML or CSS file? Read a software README file? Alter a configuration file on your computer? Read RDA listserv postings? How about search-and-replace the same niggling little error in fifty HTML files? Need to blog or wiki something, but hate typing into a box on a web page (not least because the web page can't save your work)?

A text editor will do all these things (and more!) quickly, quietly, and efficiently. Trust me, you will fall in love with a good one.

That said, if your favorite techie tries to get you to learn emacs or vi, run swiftly in the opposite direction; screaming is optional. These programs are bizarre holdovers from the early days of UNIX, and they are not for casual users. You can find a better fit.

Features to look for include:

  • syntax highlighting/coloration (this will, for example, turn HTML tags pretty colors to set them apart from text)
  • search-and-replace over multiple files
  • a "find differences between two files" function (often called "diff")
  • Unicode support (at the very least, it should be able to read and write UTF-8)
  • save to an FTP server (great for quick changes to websites)
  • regular-expression search and replace

That last item, sometimes called "grep," is a way to search-and-replace on patterns in text. It's a little too complicated to explain here (I used to have a tutorial up; will have to repost it sometime), and there is a learning curve involved, but a little bit of study will offer rich returns in what you can do to fix up old web pages.

The gold-standard for Windows is UltraEdit, which I used for years. Before buying it, however, try out the free Crimson Editor. For Mac, BBEdit is what folks swear by, but I'm pretty much content with the free version, TextWrangler.

Wikipedia has a longer list for the interested.

So the next time you're considering starting up Dreamweaver to make one little change to a web page, try a text editor instead. I think you'll be glad you did.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

For many years my favorite (for Windows) has been NoteTab Pro by Fookes Software:

http://www.notetab.com/

With built in support for HTML Tidy, BK Colour Coder, Xenu Link Sleuth, etc. But it does not have Unicode support and a new version hasn't come out in nearly three years.

I spend more time in TextWrangler than just about any other application. I use it for everything I can, only copy and pasting to Word when absolutely necessary.

Getting perhaps a little off-topic, check out these other text-lovin' links:

  • Life inside one big text file from 43Folders
  • the plain text page on the 43Folders wiki
  • Markdown, the nifty text-to-html conversion utility. Write human-readable text in your editor, run markdown, and get valid (X)HTML output. Very handy.

I still use Pico in the shell for a lot of my editing and just have at my web pages online. It's not for everyone, but people shoudl know there's usually something beyond vi and emacs for editing files on a Unix server.

Oh, absolutely; I do too. Pico (or its cousin nano) is definitely the stuff for text-editing on Unix.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.