Restoring proper TextMate bindings for RoR and RSpec

If you cannot get TextMate to use the correct bundles for Ruby on Rails and RSpec code, then you may have manually modified the bindings in a way that confuses TM.

These instructions will fix the problem.

Ubuntu server: mounting a USB drive

Follow these directions!

In a nutshell, for an NTFS drive:

$ sudo fdisk -l
$ sudo mkdir /media/myusb
$ sudo mount -t ntfs-3g /dev/sdb1 /media/myusb
$ sudo umount /media/myusb

dot-underscore files when macos copies to other file systems

In certain situations, copying files from the Mac file system to a different fs (e.g. to NTFS via NTFS-3g) results in the creation of extra 4KB-long files with names that begin with ._

Not sure how to prevent this. Look at the comments in this post.

To erase all those files from a directory tree:

$ rm */._* -R -v

(careful...)

Also see this for a terminal command that merges ._s with the original file

Problem connecting to a MySql server

While trying to connect MS-Access via ODBC to a mysql server, I kept getting this error:

connection failed mysql 10060

The page that explained the problem is:

http://forge.mysql.com/wiki/Error2003-CantConnectToMySQLServer

The default /etc/mysql/my.cnf has

[mysqld]
...
bind_address=127.0.0.1
...

which must be commented out for a remote client to gain access to the server

HTML cleanup with regexp and TextMate

to remove all spans: cmd-F, activate regexp, then:

Find:    <span.*?>(.+?)<\/span>
Replace: $1

the question marks prevent greedy matching

Autotest config

What seems to be working for me is the following:

group :development, :test do
  gem 'rspec-rails'
  gem 'webrat'
  gem 'autotest'
  gem 'autotest-growl'
  gem 'autotest-rails'
  gem 'cucumber-rails'
  gem 'factory_girl_rails'
  gem 'mocha'
  gem 'launchy'
end

And in ~/:autotest

require 'autotest/growl'
Autotest::Growl::clear_terminal = false
Autotest.add_hook :initialize do |at|
  at.find_directories = ['./features', './spec', './app', './lib']
end

The hook selects directories to watch. The default setup caused autotest to run features continuously

Setting up SSHFS connections

First, make sure you can ssh to the server

On the local machine (universe must be enabled):

$ sudo aptitude install sshfs
$ sudo chmod +x /bin/fusermount
$ mkdir /home/giuseppe/remote
$ sudo modprobe fuse

the last command loads fuse. In order for this to happen automatically at startup:

$ sudo cp /etc/modules /etc/modules_bak
$ sudo sh -c "echo 'fuse' >> /etc/modules"

Now the actual mounting:

$ sshfs the.remote.machine:/shared/path /home/giuseppe/remote