Re: call external editor from git-gui?

From: Karl Hasselström <kha@treskal.com>
Date: Aug 14, 2007, 07:00 UTC
Message-ID: <20070814070000.GA12052@diana.vm.bytemark.co.uk>
In-Reply-To: <20070814045511.GF27913@spearce.org>

On 2007-08-14 00:55:11 -0400, Shawn O. Pearce wrote:

Show 9 quoted lines

> Karl Hasselstrm <kha@treskal.com> wrote:
>
> > git-gui is very good at composing commits. But for writing the
> > actual commit message -- especially if it's long and needs
> > paragraph reflowing, indentation, and so on -- I vastly prefer
> > emacs over git-gui's text field.
>
> Yea, I've been thinking about adding fancy features like those. But
> been lazy.

Yeah, every time I read the git list, I think to myself, "Wow, Shawn sure is lazy!" :-)

You do a lot of seriously useful work on git.

> Spawning the user's preferred editor would be a nice way to get some
> of that.

Mmm. I wouldn't call it a _nice_ way: popping up an external program just to get the right text editing behavior. More like the _only_ way, if the user is picky enough.

Show 5 quoted lines

> An annoying work-around would be to run your editor to create/edit
> .git/GITGUI_MSG (or .git/MERGE_MSG) then hit Rescan in git-gui. It
> loads that file into its editor buffer if the editor buffer is empty
> or has not been modified from within git-gui since the last time the
> file was read.

I just tend to git-commit --amend to accomplish that.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle