Biodegradable Geek

Easily Installing Vim 7.2 From Source

Vim 7.2 beta was released last month, and 7.2 is now stable. First check to see if your distro offers a package, and if not, follow these simple instructions on how to install it from source, from the vim7.2 subversion branch. cd /tmp/ svn co https://vim.svn.sourceforge.net/svnroot/vim/branches/vim7.2 cd vim7.2/ ./configure --with-features=huge --enable-gui=gnome2 --enable-cscope --enable-pythoninterp make Now you can use sudo make install [...]SHARETHIS.addEntry({ title: "Easily Installing Vim 7.2 From Source", url: "http://biodegradablegeek.com/2008/08/easily-installing-vim-72-edge-from-source/" });

“Exclusive Domain Investments” Emails are Spam

I recently got an email in my junk folder (I browse it for false positives sometimes) from “Exclusive Domain Investments,” a supposed domain brokerage firm representing a client interested in buying one of my domains. It’s not a scam, but it’s clever. Here’s the email: FROM: “Exclusive Domain Investments” <domianinvestor1999@gmail.com> SUBJECT: Is <domain removed> for sale? Hello, One [...]SHARETHIS.addEntry({ title: "“Exclusive Domain Investments” Emails are Spam", url: "http://biodegradablegeek.com/2008/08/exclusive-domain-investments-emails-are-spam/" });

Workaround for “ImportError: cannot import name compat” issue in Trac 0.11.x

I had used Trac 0.10.4 for awhile before upgrading to 0.11. First time around I had no problems, but on a new server, a fresh install of 0.11.1 was giving me this error when I visit certain pages: [Sun Aug 10 19:41:57 2008] [error] [client 69.204.200.139] PythonHandler trac.web.modpython_frontend: Traceback (most recent call last):, referer: http://issues.biodegradablegeek.com/congen9 [Sun Aug [...]SHARETHIS.addEntry({ title: "Workaround for “ImportError: cannot import name compat” issue in Trac 0.11.x", url: "http://biodegradablegeek.com/2008/08/workaround-for-importerror-cannot-import-name-compat-issue-in-trac-011x/" });

Has vim/rails.vim been crashing lately? Here’s why.

If you are experiencing segmentation faults with vim and rails.vim, it may be due to this bug, which appeared after 1.7.127, but has been resolved in 1.7.147 (patch log). To check if your installation has this bug, type the following (cred goes to Ralph) in vim: :r ~fo<tab> (’fo’ being the start of a username present [...]SHARETHIS.addEntry({ title: "Has vim/rails.vim been crashing lately? Here’s why.", url: "http://biodegradablegeek.com/2008/08/has-vimrailsvim-been-crashing-lately-heres-why/" });