From: Jeff King <peff@peff.net>
To: "Suraj N. Kurapati" <sunaku@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC v3] git add -i: Answer questions with a single keypress
Date: Fri, 7 Nov 2008 14:19:10 -0500 [thread overview]
Message-ID: <20081107191910.GA15218@coredump.intra.peff.net> (raw)
In-Reply-To: <200811060815.16797.sunaku@gmail.com>
On Thu, Nov 06, 2008 at 08:15:16AM -0800, Suraj N. Kurapati wrote:
> v1 and v2 make the mistake of setting raw mode, which prevent the user from
> pressing Control-C to exit the program. v3 fixes this by using cbreak mode.
OK, makes sense.
> The git-svn.perl script also uses Term::ReadKey. Since it is already in the
> git source repository, I thought it was okay to use Term::ReadKey.
We are not always consistent with such things, and git-add--interactive
is a little "more core" than git-svn, I think. Still, maybe I am being
overly cautious. We can always try it and see who complains. ;)
I think considering this improvement:
> > - This only enhances one particular input, the patch loop. It is
> > probably worth being consistent and allowing these behavior for other
> > menus (though the numeric inputs are a bit trickier).
>
> Understood.
it makes sense to factor the ReadKey procedure into a separate function
anyway. At which point it should be easy enough to substitute in the
original behavior if there is no ReadKey.
Side note: I don't know if such people exist, but I suppose it is
possible that somebody would _prefer_ the old behavior. In which case
factoring it out will also make it easier to predicate the behavior on a
config variable, if people want that.
-Peff
prev parent reply other threads:[~2008-11-07 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 6:15 [PATCH/RFC] git-add--interactive.perl: Answer questions with a single keypress Suraj N. Kurapati
2008-11-05 6:31 ` [PATCH/RFC v2] " Suraj N. Kurapati
2008-11-05 17:59 ` [PATCH/RFC v3] git add -i: " Suraj N. Kurapati
2008-11-06 8:42 ` Jeff King
2008-11-06 16:15 ` Suraj N. Kurapati
2008-11-06 17:06 ` Junio C Hamano
2008-11-07 19:19 ` Jeff King
2008-11-07 19:19 ` Jeff King [this message]
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=20081107191910.GA15218@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=sunaku@gmail.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