Re: $EDITOR idea

cmpilato@collab.net wrote:
>
> I don't know about you, but I have to edit each of those lines anyway
> right now because the paths are always absolute ones. And they always
> have some one-letter code that doesn't actually end up in my final log
> message. And they are rarely in the order that I want them to be in.
> In other words, I always end up using a quick macro to hack off the
> first so many characters of, and prepend '* ' to, each line anyway. 4
> more characters to remove is a negligible cost.
>
> You have the power to set $EDITOR to anything you want to -- set it to
> a powerful editor that you know how to use. :-)

Yes, something like this for example :
    SVN_EDITOR='vim -c "%s,SVN: [ADM] *$HOME,,"'

On this subject, I'd like to propose an alternative lightweight
solution.

The temporary file opened by the editor has currently a name
of the form "msg.NNNNN.NNNNN.tmp". If someone wants to configure
its editor to run a macro specifically on svn commit temp files,
it may be useful to have a temporary file with a more recognizable
name (e.g. "svncommit.NNNNN.NNNNN.tmp") for a programmable editor.
Yet another way to configure your svn_editor. One's macro could
even run "svn diff" if it's really wanted.

My 2 cents --

-- 
Rafael / just another perl/vim hacker
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org