From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 2/2] prompt: respect GIT_TERMINAL_PROMPT to disable terminal prompts
Date: Thu, 4 Dec 2014 16:01:49 -0500 [thread overview]
Message-ID: <20141204210149.GB19953@peff.net> (raw)
In-Reply-To: <xmqqy4qntgs6.fsf@gitster.dls.corp.google.com>
On Thu, Dec 04, 2014 at 10:24:09AM -0800, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > diff --git a/prompt.c b/prompt.c
> > index e5b4938..8181eeb 100644
> > --- a/prompt.c
> > +++ b/prompt.c
> > @@ -57,11 +57,19 @@ char *git_prompt(const char *prompt, int flags)
> > r = do_askpass(askpass, prompt);
> > }
> >
> > - if (!r)
> > - r = git_terminal_prompt(prompt, flags & PROMPT_ECHO);
> > if (!r) {
> > - /* prompts already contain ": " at the end */
> > - die("could not read %s%s", prompt, strerror(errno));
> > + const char *err;
> > +
> > + if (git_env_bool("GIT_TERMINAL_PROMPT", 1)) {
> > + r = git_terminal_prompt(prompt, flags & PROMPT_ECHO);
> > + err = strerror(errno);
> > + } else {
> > + err = "terminal prompts disabled";
> > + }
> > + if (!r) {
> > + /* prompts already contain ": " at the end */
> > + die("could not read %s%s", prompt, err);
> > + }
> > }
> > return r;
> > }
>
> I wish this covered a lot more than just this part from an
> end-user's point of view, but this is definitely one of the most
> important code paths the mechanism should cover.
Which parts do you mean? Stuff like "git add -i"? I agree it might be
nice to turn that off, but it is a little bit of a different beast, in
that it reads from stdin. The git_prompt code is unique in accessing
/dev/tty directly, which makes it hard to shut off.
I don't know of any other code in git that (and it is used in
many spots due to calls into the credential_fill code).
I suspect there's similar code in git-svn that comes from the svn
library, and it might be nice to cover that, too.
Anyway, I'm happy to give other prompts the same treatment, but I think
we can wait and add them as they are noticed.
-Peff
next prev parent reply other threads:[~2014-12-04 21:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 0:03 Disabling credential helper? brian m. carlson
2014-12-03 0:59 ` Jonathan Nieder
2014-12-03 1:21 ` Jeff King
2014-12-03 1:29 ` Jonathan Nieder
2014-12-03 1:36 ` Jeff King
2014-12-04 1:33 ` Jeff King
2014-12-04 6:07 ` Junio C Hamano
2014-12-03 17:14 ` Junio C Hamano
2014-12-04 0:42 ` brian m. carlson
2014-12-04 3:42 ` [PATCH 0/2] disabling terminal prompts Jeff King
2014-12-04 3:46 ` [PATCH 1/2] credential: let helpers tell us to quit Jeff King
2014-12-04 3:52 ` [PATCH 2/2] prompt: respect GIT_TERMINAL_PROMPT to disable terminal prompts Jeff King
2014-12-04 18:24 ` Junio C Hamano
2014-12-04 21:01 ` Jeff King [this message]
2014-12-04 21:33 ` Junio C Hamano
2014-12-05 9:10 ` Jeff King
2014-12-05 17:37 ` Junio C Hamano
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=20141204210149.GB19953@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=sandals@crustytoothpaste.net \
/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).