From: Seth Falcon <sfalcon@fhcrc.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Seth Falcon <sfalcon@fhcrc.org>, git@vger.kernel.org
Subject: Re: suggestion for git rebase -i
Date: Sat, 28 Jul 2007 08:52:40 -0700 [thread overview]
Message-ID: <m2vec4seyf.fsf@ziti.fhcrc.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707280941380.14781@racer.site> (Johannes Schindelin's message of "Sat\, 28 Jul 2007 09\:43\:15 +0100 \(BST\)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Why? This is an implementation detail, and should not concern the
> user.
In the context of an existing editing session, the name of the
tempfile is visible and relevant to the user (not just an
implementation detail). For example, the tempfile name is useful when
multi-tasking and one needs to get back to the buffer. As another
reply pointed out, the name could also be used for editor mode
customization.
So. When editing a commit message, the buffer is named
COMMIT_EDITMSG. When editing a rebase -i buffer it is named todo. Is
this a real problem? Of course not. But I think a slightly more
descriptive name makes sense -- especially if other commands gain
interactive modes and a user might have a number of them going at once
(in different repos, e.g.).
+ seth
next prev parent reply other threads:[~2007-07-28 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 4:58 suggestion for git rebase -i Seth Falcon
2007-07-28 8:43 ` Johannes Schindelin
2007-07-28 8:45 ` Jeff King
2007-07-28 8:58 ` Jeff King
2007-07-28 15:52 ` Seth Falcon [this message]
2007-07-28 20:09 ` Johannes Schindelin
2007-07-28 23:11 ` Seth Falcon
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=m2vec4seyf.fsf@ziti.fhcrc.org \
--to=sfalcon@fhcrc.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).