I was just trying to get some Python to work and decided to wrap it in a shell script in Cygwin on Windows XP so that I wouldn't have to convert a batch file to a shell script later on when I copied it to a Unix server.
Of course, when I ran the script, Bash complained that the interprerter mentioned in the #! line wasn't there. In a fit of non Unix compatibility I just replaced /usr/bin with the correct path of my Python exe on Windows.
I should have tested this before updating all my files as Bash choked on the spaces in the path to my Python exe. After some mad Googling to find out how to escape this properly I gave up and did what I should have done in the first place.
I went over to my Cygwin's /usr/bin and made in a symbolic link to the Python exe in my Windows installation of Python. For some reason, I didn't expect symbolic links made in Cygwin on Windows to work but it worked perfectly.
Also, as usual, I reversed the arguments for "ln" the first time I tried to make the link. It always seems backwards to me and the help text doesn't make it obvious which is the source and which the destination.
What I found interesting was that I assumed that putting in the windows path would work the most quickly and it would be less effort to do a temporary fix which I would have to fix later than to try and use "ln".
The other day I finally gave up on Outlook at work and decided to use
Becky! there too. I found a utility on SourceForge to convert Outlook
files into something more standard but it didn't export all the headers
so I Googled around and found the one true way to get your mail out of
Outlook; is Mozilla!
Mozilla stores it's mail in "mbox" format which every other sensible
mail program and scripting language supports and more importantly
it can import your mail from Outlook. As far as I can tell, it is
perfect.
Things would have gone smoothly if I had hadn't had so many folders in
Outlook as each one became a separate mbox in Mozilla.
Overall a great success