Bill Powell Is Alive
{ Man Found Alive With Two Legs }

A personal blog about Linux and literature, distributism and Catholicism, adventures in permaculture, and being alive.

Recent posts

Blog, Linux, Emacs, Vim

2010 Jul 18 Sun

Leaving Vim(Outliner) for Emacs
Vim is the best of both worlds. In theory.

Linux

2010 Jul 08 Thu

SysAdmin Toolbox
Useful sites for system administrators.

Linux, Op-ed

2010 Jul 05 Mon

Proud to be Computer Illiterate
Stop apologizing because you don't know everything about computers.


Leaving Vim(Outliner) for Emacs

by Bill Powell | updated: 2010 Jul 18 Sun | published:
tags: blog, linux, emacs, and vim

As I mentioned awhile back, I've switched from Vim to Emacs. Vim and Emacs are both text editors. If you don't think text editors are awesome, please go read the first half of "A Hymn to Vim," wherein the discerning reader may discover the glories of pure text. When you get to "Why Vim? What I like best …", you can come back. Or actually, go straight over to Org Mode, and find out how plain text can dance.

Still here? Then you know how unusual it is to go from Vim to Emacs. At least, it seems unusual. I found several articles about leaving Emacs for Vim (and many more articles by Vim people about how awful Emacs must be), but I had a hard time finding tales of people leaving Vim for Emacs. Though, I do see allusions on the org-mode list. Maybe Emacs people don't like to blog about it. Or maybe I just had a bad search day.

Anyhow, this is why I switched.

vi Lightning

"Emacs vs. vi" is supposedly an ancient feud, the venerable Editor War. Considering that Unix time only began in 1970, maybe we geeks have to take tradition where we can get it.

But notice I wrote vi, not Vim.

True, what first got me excited about Vim were the best parts of vi: the magic of modal editing and single key commands. Here, at last, was a language of mastery over text, potent and preternaturally fast. You could craft whole commands, like go back two words and delete to the end of the line, and compress them into a single word: 2bd$.

Well, <Esc>, and then 2bd$, and then i or a to get back to Insert mode. But still. Lightning.

Vim(Outliner) Magic

However, as I used Vim, my excitement soon hinged on features like syntax highlighting and color schemes. And then I started adding things: magical snippets to .vimrc, incomprehensible but effective scripts from www.vim.org. Before long, I was trying to browse the Internet from within Vim. That one didn't work out.

What did work out was VimOutliner. Wow. What a sweet outliner. Of all the scripts I ran on Vim, VO was king. Sometimes it felt like I was running VimOutliner, and opening a Vim buffer when I needed it. That vi lightning could now blast whole trees of text. I wrote as much as I could in VO files. I even tweaked the script so that colorschemes would work, and I could see my outlines in glorious inkpot (or whatever).

I enjoyed and relied on Vim and VimOutliner for years, and nothing will ever change that. They were a free gift, a collaboration from so many people I'll never meet. If you are one of these people—thank you. So much. I will always be grateful.

So why switch, then? Well, the astute reader may have noticed that all this "vi(m)" goodness was entirely parenthetical—you couldn't do any of this in plain vi. Where was my youthful asceticism? My delight in the clean lines of sheer modal editing?

Of course, that's the whole point of Vim: you can have all that addon emacs-y goodness and remain a fierce, modal monk. Best of both worlds. In theory. But what if the fountains of addon goodness ever went dry?

Trouble in addon land

Meanwhile, I had a problem. I was trying to clock my work intervals, and every program I tried made it almost impossible to correct mistakes. It was like punching a time card. Oh, you left it running while you switched tasks, did you? Well, I'm sorry, Mr. Powell, the log files are etched in granite—or at least, deep in an ugly database. One CLI app was sensible enough to store the intervals in a plain text file, but … in epoch time. Great. Apparently, if you weren't geek enough to convert your missed afternoon break time to the number of seconds elapsed since 1970, in your head, you didn't deserve to correct your record.

Of course, I could write some script to do this conversion for me. But why stop there? What if could clock my work intervals in a big VO file, with proper, human-readable datestamps? So I tried to extend VO. My knowledge of VimScript was minimal—well, rudimentary—well—nonexistent. I forged ahead, of course, and cobbled together something that did a decent job for multiple years. Strangely, though, it was clunky and limited. And needed a shell script (eventually improved to Perl) to process it.

Where to turn for help? VimOutliner had (has) a sporadic but spirited mailing list. Surely, since they knew what they were doing, they could clean this up in short order. Vim could do anything…couldn't it?

To be continued…

SysAdmin Toolbox

by Bill Powell | updated: 2010 Jul 08 Thu | published:
tags: linux

Whenever I can, I use open source software. But some web sites out there offer pretty useful tools. Here are a few of the ones I use. There aren't many yet, because I really do use software on my own computer for most things. But I'll add more as I find them.

As a title, "SysAdmin Toolbox" is probably false advertising. I've only got a few links here right now, and one of them is for making printable calendars. But hey, system administrators have to stay organized too. Besides, the point is that each link here actually does something, instead of just serving up a bunch of moldy old articles, like some dumb blog.

DISCLAIMER: I have no connection to any of these sites. In fact, for the bigger ones, I only know about the page I'm linking. For all I know, the rest of each site is a gigantic MLM scheme pushing toxic deodorant and counterfeit pennies. But I hope not.

PDF Generation

PDFCalendar.com 2010-07-08 Thu

Customize a calendar to print on a standard sheet of paper. You can set the number of weeks, which means you can see two months or more on a single sheet. No registration crud or anything; just set your parameters and download the calendar.

And no, as far as I know, these PDFs won't take over your computer. They're clean. Hey, don't laugh! You really do need to scan even PDFs before you open them. In the wrong viewer, an evil PDF can execute arbitrary code. Seriously! Oh, never mind.

Internet

What is my IP 2010-07-08 Thu

Find out your IP address. Right now. Even if the numbers don't mean anything to you, it's kinda cool. It's also a friendly reminder that almost every single site you touch today will log this unique, identifiable number. Happy browsing. :)

Sorry, these links are all turning into teaching moments. I guess this is a blog, but still…

Email

Blacklist check 2010-07-08 Thu

See if your server is on major spam blacklists. Probably don't need this unless you're managing an email newsletter. And if you do have a problem, it's probably your ISP. Unless you're a spammer. But when you do need this, it's awesome.

Spam Gourmet: Disposable E-mail addresses 2010-07-08 Thu

Pick a username (say, fernbazaar), and you can make up disposable addresses on the fly whenever someone forces you to register. Like free-ebook.fernbazaar@spamgourmet.com, or just-the-song.fernbazaar@spamgourmet.com, or whatever. The first three emails to each address will be forwarded to your real, secret email address. That's long enough to get your confirmation link --- but when the address gets sold to spammers, you're long gone.

As another option, you can configure some sites as "trusted senders." For instance, you'll keep getting that newsletter from a trusted site, but if the address ever falls into another site's hands, you're protected.

I wish I'd known about this back in 2003.

Envoi 2010-07-08 Thu

A list of links is never done,
But reading lists is never fun.
You scroll and scroll and scroll the page,
Till boredom ferments into rage.
"I'm wasting time! My life's a leak!
I'll still be reading this next week!
Skip to the end! I'm going home!"
But here, at least, you found a poem. Huzzah!

Proud to be Computer Illiterate

by Bill Powell | updated: 2010 Jul 05 Mon | published:
tags: linux and op-ed

Stop apologizing because you don't know everything about computers. You know lots of other stuff. Computers will slurp every waking moment if you let them. Don't. And relish that choice.

When you go to the doctor, you don't say, "I have this pain in my shoulder—I'm sorry, I don't know the Latin name for it—dangit, I really should—man, what am I doing with my life? I could be working my way through Gray's Anatomy."

But computers? People can be so apologetic.

Maybe they've had bad experiences with other geeks. It used to bug me that most computer users don't seem to know much more about them than I know about my car. I tried not to let that show. I hope.

But that raised an interesting question: why didn't I know much about my car? Or my plumbing? Or my shoulder?

Now, there's a sparkling case to be made for plumbing the depths of plumbing. I can see Chesterton making that case. I can see him blazing and dancing through a scintillating essay, leaping from T-joints to ball-and-joints to piston joints, laying bare the wonders that support our crappiest days. Fairylands awaken on every side.

He's right, of course. And then I see him finishing that essay, sending it off, and starting right in on something for G.K.'s Weekly. And then he talks and talks and talks, dictating all day, until he's sick of it. And then he goes drinking with Belloc.

Because he's a writer. That's what he does. All day.

I don't mean Chesterton was a hypocrite. He forgot more about literature and philosophy and history than I will ever know. But I'm not sure how much he knew about floor joists.

Yes, we should know about cars and carpentry—and computers. With 20 years or so in school, we really should. And if you've got kids, maybe you can help things turn out differently for them.

But if you're reading this, you're probably done, or nearly done, with school. Most of us don't start learning much useful until college, and maybe not until long after, sometime in our mid-twenties.

Learning takes time. Whatever you're learning these days, it may not be computers. Yet somehow, computers are apparently supposed to be obvious.

I only found out recently that "computer illiteracy" seems to have started life as a marketing phrase. But doesn't that makes perfect sense? I mean, does anyone talk about "plumbing illiteracy"? No, plumbing is somehow faintly humorous. But I bet you would rather take your chances without a computer than without plumbing. (Actually, at one point, I went without plumbing and kept the computer, but that's another story.) I haven't studied the history of indoor plumbing, but I bet that no vast marketing campaign was required to convince people that indoor faucets might be handy.

But with computers, we got stuck with this concept of "computer literacy." And the phrase keeps morphing. I don't know what it meant ten years ago—maybe being able to buy a computer—that was key—and after that, whatever, just turn it on. Today, it's like, you can't design your own website? You don't know HTML? CSS? PHP? Can you even read? What are you doing with the Internet?

Somewhere along the line, I acquired the geek hat, and so yes, I personally am irritated that people don't know more about computers. Their lives (and mine) would be so much easier, safer, more private, and more fun.

But they might be even better off growing fruit trees and chickens.

So if you are "computer illiterate," it is precisely because you've been doing other things. Becoming an electrician. Raising several children. Publishing graphic novels. Whatever. So keep doing it. Okay, maybe start backing your data up more than once a decade, but otherwise, if you like what you're doing, keep it up. And hold your head high.


This page last generated: Sun Jul 18 14:11:02 -0400 2010