From: Ted Pavlic <ted@tedpavlic.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] contrib: A script to show diff in new window while editing commit message.
Date: Wed, 21 Jan 2009 22:39:55 -0500 [thread overview]
Message-ID: <4977EA8B.8000403@tedpavlic.com> (raw)
In-Reply-To: <7vy6x4b48e.fsf@gitster.siamese.dyndns.org>
> * Some people would like two-buffer operation and they may use this
> script as their core.editor.
That's what I do, and evidently that's what enough Mercurial users do to
warrant them putting "hgeditor" in their main distro (not even in the
"contrib" directory). I just figured there must be at least a few other
people out there like me, but maybe I'm wrong. <?>
> * Other people (including me) would find it very natural to use "\C-x 2"
> if they need to look at two places of the same buffer, because that is
> what they are used to do when editing a long file every day. They just
> use "commit -v" without bothering with this script.
As I mention in the script, splitting windows (which is easy to do in
Vim) is another very natural way to go. That being said, not all editors
have terrific split window support. Plus, if you're going to do it
often, it makes sense to wire up your editor to do it for you each time.
> * Yet other people (like Dscho) would find it too late to have a chance
> for final review when writing a commit log message anyway, and won't
> use either.
I'm not using the diff as a code review. I'm using it to help me make
sure my commit message is complete.
> Having said that, if the lack of "final chance to review the diff" in some
> StGIT subcommand is the real problem you are trying to solve, I think it
...
Having the "stg edit" support is just a bonus (for me). The main point
was showing how to use GIT_EDITOR to bring up a split window. As with
Mercurial's hgeditor, part of the point of the script is to demonstrate
how to customize the commit process.
Thanks --
--Ted
--
Ted Pavlic <ted@tedpavlic.com>
Please visit my ALS association page:
http://web.alsa.org/goto/tedpavlic
My family appreciates your support in the fight to defeat ALS.
next prev parent reply other threads:[~2009-01-22 3:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 20:47 [PATCH] Added giteditor script to show diff while editing commit message ted
[not found] ` <0E82F261-2D96-4204-9906-C5E8D47E9A5D@wincent.com>
2009-01-21 21:07 ` Ted Pavlic
2009-01-21 21:46 ` Johannes Schindelin
2009-01-21 22:33 ` Ted Pavlic
2009-01-21 22:45 ` [PATCH] contrib: A script to show diff in new window " Ted Pavlic
2009-01-21 23:59 ` Junio C Hamano
2009-01-22 3:39 ` Ted Pavlic [this message]
2009-01-22 3:50 ` Ted Pavlic
2009-01-22 7:49 ` Junio C Hamano
2009-01-21 22:52 ` [PATCH] Added giteditor script to show diff " Johannes Schindelin
2009-01-22 1:46 ` Ted Pavlic
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=4977EA8B.8000403@tedpavlic.com \
--to=ted@tedpavlic.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).