From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: call external editor from git-gui?
Date: Tue, 14 Aug 2007 00:55:11 -0400 [thread overview]
Message-ID: <20070814045511.GF27913@spearce.org> (raw)
In-Reply-To: <20070810153008.GA31759@diana.vm.bytemark.co.uk>
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. Spawning the user's preferred editor would be a
nice way to get some of that.
> It seems to me like it would be straightforward to have a button or
> something to launch the user's favorite editor for editing of the
> commit message -- after all, git even knows what editor that is!
Probably. git-gui already has the data from .git/config loaded in
memory, it should be fairly simple.
> Unfortunately, with my tcl expertise, this is likely a whole-weekend
> project, so I probably won't try to build it myself in the near
> future.
With my busy schedule its unlikely to happen anytime soon either.
But I've added it to my todo branch. Sometimes things on that list
get accomplished. ;-)
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.
--
Shawn.
next prev parent reply other threads:[~2007-08-14 4:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 15:30 call external editor from git-gui? Karl Hasselström
2007-08-14 4:55 ` Shawn O. Pearce [this message]
2007-08-14 7:00 ` Karl Hasselström
2007-08-15 18:22 ` Jan Hudec
2007-08-15 18:31 ` Uwe Kleine-König
2007-08-15 18:38 ` David Kastrup
2007-08-16 7:59 ` Mike Ralphson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070814045511.GF27913@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).