Skip to main content

Posts

Showing posts from January, 2010

Screen for long remote tasks

use

to start a session named mySession on your remote machine. Start the things you want to run, for example a

close the shell by quitting terminal (don't Ctrl C out!)
When you come back, and want to see how far your make went, attach to the old screen with

If you don't remember what you called the session, try

Working here

Now I know where I want to work, it's just a matter of working hard enough to get there.

Git pushing to multiple repositories

If for some reason you have to push to multiple repositories, add an alias to your .git/config (obviously you don't want this in your ~/.gitconfig):


The exclamation mark runs the alias as a command, without an exclamation mark, it's assumed that you run a git command.


results in a change in your ~/.gitconfig

which you can delete with

or delete all aliases.

Vim for irb

Ever used irb and wished you had safed your commands or could edit them using Vi? Ever tried something new in irb, and then had to painfully copy and paste it to the .rb file? Slime.vim from Jonathan Palardy will be your new best friend.

Slime.vim lets you send highlighted text to a different terminal. This means you can write a few commands, send them to a terminal running irb, notice you want to change something in your first command, modify that line in Vi and resend it to irb, and so on.

Put slime.vim into ~/.vim/plugins

In one terminal:

1. start a named screen

2. name the window

You'll be prompted for the window's name, "Set window's title to:"
irb_window
3. start irb

In a different terminal, start vi and type irb commands, highlight one or multiple commands (ESC V to highlight the current line, ESC vip to highlight a paragraph), type C-c C-c to execute the highlighted text in the other terminal. The first time you'll be prompted for session and window, en…

The pink was just a little too much