Use JungleDisk. It works on Windows, Mac OS X and Linux. It stores things to Amazon EC2 which is pretty cheap per gig per month. Keep a backup on a single drive at home, and either EC2 or your drive will go down, less likely both simultaneously. Restore from the 'net if your local copy dies. I store all my family photos, work documents and other important things there. If you don't like the monthly fee, you can always go through the hassle of backup to tape, or maintaining an account on two or three friends' servers and hope they don't shut things off. For me, a cheap network drive (non redundant) for a local copy, and EC2 for a remote, offsite copy, enabled by JungleDisk, which can also encrypt my data, is worth the $0.15/GB/month. I pay less than $10/month for 50 some-odd gigs of data I'm backing up. Probably makes less sense if you are backing up terabytes of data, but if you're doing that, you'll probably be willing to back up, then drive it off-site, for super-safe keeping.

Hmm. Except that the problem of SQlite being updated by two or more people at the same time would create problems. Unless BugIDs were md5 hashes, an insert would likely cause problems. And even md5 hashes have collisions, though pretty unlikely even if you have 100,000 bugs.

This is cool, your code can be free. But unfortunately you're still stuck with hosting the documentation on a central website of some sort. I'm hopeful someone will whip up a standard for hosting the documentation website. IE PHP + SQlite + GitTorrent docRoot == Distributed website. Now several websites could support any GitTorrent-hosted documentation. Go to any GitTorrentDoc-enabled website, type in the .torrent of the repository, and blam -- the server pulls it down (or has it already cached) and you can page through the fully-dynamic docRoot. Could even contain Trac or something, so all the bug tracking is also in the GitTorrent repository.

Or to reformat the whole file with proper indent rules for that filetype:

gg=G

Then after you've highlighted what you want, you can then type other commands.

shift-v
j j j j j
:s/foo/bar/g

replaces foo with bar in only the 5 lines you've highlighted.

Wow, that post was actually extremely useful! You'd think after 16 years of using VIM I'd have tried ":help sex" but no.

I love to use the formatting that is included. Set your filetype and syntax correctly, then type:

gg=G

Now your indent preferences, as well as the filetype specific indenting rules are applied to your whole file. Great for getting a piece of code that has horrible standards, just gg=G and you've formatted your file according to your tabstop requirements.

What I just now learned is how it all works.

gg -> Go to the first line of the file.
= -> runs 'equalprg' and if empty, either 'lisp' 'cindent' or 'indentexpr' are run.
G -> Do something from where you are now to the end of the file.

Will not work if you've set equalprg to something else.