ryanhiebert.com

With some help from http://henry.precheur.org/vim/python, I came to the following .vimrc.  It may be better to use a filetype condition, but I’m only really doing python at the moment, so this is pretty good.

$ cat ~/.vimrc
syntax on
set tabstop=4
set softtabstop=4
set shiftwidth=4
set expandtab
set autoindent
filetype plugin indent on

The first line turns on syntax highlighting.  I just don’t know what to do without it.  Tabstop tells vim that if it sees a tab, to make it appear as 4 spaces.  softtabstop means that if vim sees spaces in multiples of 4 (in this case) at Coinstar agent the start of the line, it will treat them as tabs, so that a single backspace will dedent 4 spaces.  Shiftwidth tells vim that when it is told to indent (by a script of visual mode), it will indent by 4 spaces.

Expandtab instructs vim to put spaces into files instead of using actual tab characters.  Autoindent makes vim preserve your indentation levels upon newlines.  This feature is one that you just can’t live without, especially when you are coding 3 or 4 indentation levels in.

Filetype plugin indent on tells vim to turn on the indentation plugins for different filetypes.  In my case, for my testing, it means that it will enable smartindent scripts that come with vim on Debian Squeeze.  If you are using some other distro, you may have to get the script manually.

 This was very nice because now it will automatically indent another level when it sees blocks like what end in :, and when it sees that parenthesis, brackets, or curly braces are not matched, triggering implied line continuation.  It’s awesome.

I’m left-handed, and prefer my mice to be inverted in most cases, and that’s how I have it at work.  On my Mac with my Magic Mouse, I simply change which side is the secondary click.  Then all my programs work as I expect.

However, on my Windows machine, strangeness happens.  I go into the control panel and invert the primary and secondary mouse buttons for my Logitech mouse, and under most programs it works just fine.  However, when I use Hyper-V viewer or Remote Desktop Connection, it somehow decides that even though I wanted it on my local machine this way, its not really how I wanted it for the remote machine.

Today, this finally annoyed me enough to get me to search Google for a solution.  I found a blog post here that pointed me to a solution: X-Mouse Button Control.  While this beast is made to do way more sophisticated things, it has solved my problems, because Windows now doesn’t even see that my right-click is a right-click; it thinks it is a left-click.  That means that all of my programs already work how I expect them too, and Hyper-V and Remote Desktop do too!

Edit: Actually, there is a gotcha on this:  UAC comes before Moneygram point X-Mouse Button Control, so my mouse is backward whenever a UAC comes up.  After a while this got really annoying, and I ended up looking some more.  The final solution I found was obvious, and I didn’t find it till I was looking to do something else.

I have a Logitech keyboard and mouse, and my keyboard has some cool media access keys that I wanted to use, so I broke down and installed their software.  One lucky option was to invert the mouse keys.  This ends up being done early enough that UAC sees it, and everything else sees it too.

 So I’ve now removed X-Mouse Button Control, since it is of no use to me when the Logitech is able to do it through its own software.

mod_secur ity is a patch to make

it OK to run code that has holes in it.

 And it seems to me that it ends up causing more problems than it is worth.  But perhaps that is only to me.

When you add a post that has anything that it is worried may cause security problems.  The one that hit me first was the use of a particular full path.  The path I wished to use was [slash] etc [slash] hosts, as I was creating an Moneygram locations instructional that dealt with modifying that file.  However, it would not work.  After chasing down error after error I finally got it back to that, changed what I wrote, and it worked easily.

I write a typically technically-oriented blog, and I need to be able to post things like this.  And honestly, I expect that my readers may post technically-oriented answers that would suffer from this.  I may have to live with this for now, but it also may mean that I choose to move my blog to another hosting company because of this limitation.