Thanks for posting your blame alias, it’s a handy idea! I tweaked it a bit, and though I haven’t added the svn log functionality, I have made it work with 0 or more line number arguments (When you don’t supply any, it prints the entire blame output with line numbers.)


svnblame() {
if [ $# -lt 1 ]
then
echo "Please specify a file to examine for blame data."
else
resource="$1"
blame=$(svn blame "$resource" | cat -n)
if [ $# -lt 2 ]
then
echo "$blame"
else
shift
while [ $# -ne 0 ]; do
echo "=== "$resource":"$1
echo "$blame" | egrep --context=3 "^[[:space:]]*$1\b"
shift
done
fi
fi
}


alias A=’bbedit’
alias AM=’svn diff –diff-cmd bbdiff –extensions “–resume –wait”‘
alias C=’bbedit’
alias D=’true’
alias G=’svn diff –diff-cmd bbdiff –extensions “–resume –wait”‘
alias I=’true’
alias M=’svn diff –diff-cmd bbdiff –extensions “–resume –wait”‘
alias R=’svn diff –diff-cmd bbdiff –extensions “–resume –wait”‘
alias U=’bbedit’

This week I’m reviewing the total changes over about 50 revisions, when I wasn’t keeping up with my collaborator. I added ” -r848″ (the version I was caught up, before he started making changes I want to review) to the M & AM aliases, and I can now paste in a few lines from the “svn update” output to review changes one file at a time.

Note that the “--wait” is necessary, as otherwise successive diffs overwrite the .tmp file BBEdit compares against, and earlier comparisons break.

[helpers]
editor = edit.sh
diff-cmd = bbdiff
extensions = --wait --resume

to ~/.subversion/config, and can now svn diff (with or without arguments) to get BBEdit to DWIM.

Additionally, I tweaked my profile and created a helper script for programs which reject arguments (spaces) in EDITOR:

pepper@pepperbook:~$ grep -C3 PAGER bin/profile.sh
  if [ -x ~/bin/edit.sh ]
  then
    export EDITOR=~/bin/edit.sh
    export PAGER="col -b | bbedit --clean --view-top"
  else export EDITOR=vi
  fi # [ -x ~/bin/edit.sh ]

pepper@pepperbook:~$ cat bin/edit.sh
#!/bin/sh
# Edit a file in BBEdit (if available), for programs that don't support arguments in $EDITOR.
if [[ $SSH_TTY ]]
then # Remote
  vi "$@"
else # Local
  bbedit --wait --resume "$@"
fi

Now svn ci, crontab, man, etc. all use BBEdit when available, or vi when I’m logged in through a text-only connection (ssh).

Edit: bbum moved some tags around to make it more readable in the context of my rather stupid CSS.

that shouldn’t be the case. plenty of other people are using it, on Linux, Mac OS, and Windows, and with BitKeeper, CVS, and Subversion. (i don’t know of anyone seriously using the Bazaar back-end yet.)

could you report your problems to the email address in the README file, please? (or to the address i gave when entering this, which i assume you can see.)

we do have a *long* way to go to be a typical .app-in-a-.dmg Mac OS experience — it’s not obvious how we’d fit that model, and we hate .pkg packages to the extent that we never install them ourselves, so don’t expect others to. but for anyone prepared and able to build from source and put the bin/ directory on their path, we should “just work”. if we don’t, i’d like to fix it.

(sorry for the delay; a user just pointed me at this. blog comments are such an impractical way to hold a conversation!)

Looks interesting. Needs some cleanup before it is useful (to me). I look forward to checking it out.