Monday, March 28, 2005

(Starting) Remote Access remotely with VNC
Today I went to the coffeeshop and started working on some code. Except I forgot to check in a file - oops! Even more oops: the file is in the trash! Very hard to get to it via ssh.

Then I got the idea: can I launch OSXVnc from an SSH session (of course, sshing in as the user with the current window manager session)? The answer: Yes.

Read how to do this, and so much more, at the FAQ page for OSXVnc




On BBEdit 8.1
So I tried out BBEdit 8.1 today.

ROCK

If you use BBEdit and use Subversion, run. Why are you still reading this? Clicky-clicky! All of the features that the CVS menu in BBEdit has, and a few Subversion specific features (svn resolved anyone?)

On, and a nice little Text Factories menu ala the Applescript and #! menus.

Oh, yeah, I particularly like the feature where, if your svn/cvs/p4 executable isn't on your (GUI) path, you just do a default write .... to tell BBEdit where the executable is.

Nitpick: Although the supplied command is safe, and always works, I suggest the following command:

defaults write com.barebones.bbedit Subversion:SubversionToolPathOverride `which svn`

Not that those are ticks (usually found on your tilde key), not single quotes. Of course, this assumes that svn is on your PATH, which may or may not be true. I understand the error on the side of caution, just thought I'd pass the tip around.

It also fixed a bug we were going to report (but never did, or the bug disappeared on us or something) where BBEdit's syntax parser incorrectly colored ?> in PHP strings.

Woh, and BBedit now works out of the box with CVS over SSH.

I <3 Barebones