SubEthaEdit, see-tool and Subversion

Posted by dom Fri, 31 Mar 2006 10:38:00 GMT

First the basics. If you like SubEthaEdit and live in the command line some time in your computer life, you'd be happy to know that we ship a command line utility with SubEthaEdit that allows you to use SubEthaEdit as your command line editor.

The tool is called see and you can install it via the Advanced preference pane. The Install button will install the tool at /usr/bin/see - so it's ready to use directly in your standard command line path. To get detailed information about its usage, just type man see anytime after installation. (This HTML rendering of the man page was created using Bwana - a really nice tool that lets you type e.g. man:see in your browser and displays the man page.)

Xcode preference Settings.

There are a ton of nice features in the see command, the one I like most is the fact that you can pipe in and especially out of it - so you can integrate it in any unix workflow you are using. I will show a example of this in a follow up post to this.

If you are a Subversion user, you'd probably want to tell Subversion to use SubEthaEdit when editing. To have that you edit your ~/.subversion/config file and change your editor-cmd of the [helpers] section to this:

[helpers]
editor-cmd = see -w -r -j "SVN"
Now you get a nice temporary SubEthaEdit window when you do a checkin or a propedit, -w tells the see tool to wait for the window to be closed before continuing, -r makes the see tool switch back to the terminal after the job is done and -j adds a nice little SVN to the window title.

That's it for now, share and enjoy!

Posted in  | Tags , ,  | 8 comments

Comments

Leave a response

  1. Bert JW Regeer said about 1 hour later:
    There is a typo in the box, instead of a -t, it says -j.
  2. map said about 1 hour later:
    Thanks for mentioning that Bert. In fact the "-j" adds a description after the window title in brackets so you get "Controller.m [SVN]" e.g. I changed the article accordingly.
  3. Chris said about 12 hours later:
    That's very cool. I was trying to combine this tip with the previous one about using SubEthaEdit as the external editor for XCode. Any ideas on how to modify the PBXExternalEditorList entry for SubEthaEdit to get similar behavior for XCode? (mainly to make it return to XCode after closing that specific SubEthaEdit window)
  4. Bert JW Regeer said about 16 hours later:
    Cheers!
  5. leeg said 3 days later:

    The OS as shipped can do HTML manpages too...

    leeg@leegion:~>groff -man -T html /usr/share/man/man1/printf.1 > printf.html
    leeg@leegion:~>open !$
    open printf.html

    cool, non? Safari also understands the x-man-page: protocol for URIs, which is good but not great.

  6. Clayton Parker said 10 days later:

    Awesome! This is exactly what I was looking for and all I had to do was 'man see' to get the info I needed :P

    I set this up and tried to run a commit and then cancel it. I get the:

    Log message unchanged or not specified
a)bort, c)ontinue, e)dit

    But it does not accept when I type a,c,e or anything. The only thing it will accept is return and that causes a commit d'oh!

    Any idea why it doesn't accept the keyboard input after closing the see window?

    Thanks for the tip!!!
  7. Coleman Nitoy said 4 months later:

    I get the same issue. I can't use see for svn commits :-( Would love it if this worked.

  8. Consulting Online Scheduler said over 4 years later:

    This Command line tool was really great and useful for me....it makes my work more easier....

RSS feed for this post

(leave url/email »)

   Comment Markup Help Preview comment