From: Jeff King <peff@peff.net> To: Firmin Martin <firminmartin24@gmail.com> Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org, Johannes Schindelin <johannes.schindelin@gmail.com>, Erik Faye-Lund <kusmabite@gmail.com>, Denton Liu <liu.denton@gmail.com> Subject: Re: [PATCH v1 1/8] compat/terminal: let prompt accept input from pipe Date: Mon, 10 May 2021 17:32:13 -0400 [thread overview] Message-ID: <YJmmXZdwSoR+vxjw@coredump.intra.peff.net> (raw) In-Reply-To: <875yzrgr1f.fsf@Inspiron.i-did-not-set--mail-host-address--so-tickle-me> On Mon, May 10, 2021 at 06:18:36AM +0200, Firmin Martin wrote: > > Looking at the second patch, the motivation here seems to be to use > > git_prompt() for another run-of-the-mill prompt. But the right answer > > is: don't do that. In fact, we recently-ish removed a similar case in > > 97387c8bdd (am: read interactive input from stdin, 2019-05-20) that was > > likewise causing problems with the test suite. > > I actually inspired myself from the two occurrences of git_prompt in > builtin/bisect--helper.c introduced in 09535f056b (bisect--helper: > reimplement `bisect_autostart` shell function in C, 2020-09-24). > Not sure if they should also be converted to a simple fgets. Yes, I think they should be switched. It looks like since my earlier patches to "am" we have grown a git_read_line_interactively() helper. See: https://lore.kernel.org/git/pull.755.git.git.1586374380709.gitgitgadget@gmail.com/ They should probably use that (and likewise, it would make sense for git-am to switch to it). > > I think we might consider renaming git_prompt(), or adding an > > explanatory comment above it. > > I would be happy to do that. A comment along the line of 97387c8bdd (am: > read interactive input from stdin, 2019-05-20) and a "CAUTION: don't use > it for regular prompt" would suffice ? Yeah. You might want to point people at git_read_line_interactively() in the same header file, too. -Peff
next prev parent reply other threads:[~2021-05-10 21:32 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-06 16:50 [PATCH v1 0/8] format-patch: introduce --confirm-overwrite Firmin Martin 2021-05-06 16:50 ` [PATCH v1 1/8] compat/terminal: let prompt accept input from pipe Firmin Martin 2021-05-06 23:37 ` Junio C Hamano 2021-05-07 4:54 ` Jeff King 2021-05-07 5:25 ` Junio C Hamano 2021-05-10 4:18 ` Firmin Martin 2021-05-10 21:32 ` Jeff King [this message] 2021-05-11 3:38 ` Junio C Hamano 2021-05-11 6:10 ` Jeff King 2021-05-11 6:17 ` Junio C Hamano 2021-05-11 6:37 ` Jeff King 2021-05-06 16:50 ` [PATCH v1 2/8] format-patch: confirmation whenever patches exist Firmin Martin 2021-05-06 23:48 ` Junio C Hamano 2021-05-10 3:30 ` Firmin Martin 2021-05-10 7:32 ` Junio C Hamano 2021-05-11 3:17 ` Firmin Martin 2021-05-06 16:50 ` [PATCH v1 3/8] format-patch: add config option confirmOverwrite Firmin Martin 2021-05-06 16:50 ` [PATCH v1 4/8] format-patch: add the option --confirm-overwrite Firmin Martin 2021-05-06 16:50 ` [PATCH v1 5/8] t4014: test patches overwrite confirmation Firmin Martin 2021-05-06 16:51 ` [PATCH v1 6/8] t4014: fix tests overwriting cover letter in silent Firmin Martin 2021-05-06 16:51 ` [PATCH v1 7/8] doc/format-patch: describe --confirm-overwrite Firmin Martin 2021-05-07 3:32 ` Bagas Sanjaya 2021-05-10 4:22 ` Firmin Martin 2021-05-06 16:51 ` [PATCH v1 8/8] config/format: describe format.confirmOverwrite Firmin Martin 2021-05-06 22:33 ` [PATCH v1 0/8] format-patch: introduce --confirm-overwrite Junio C Hamano 2021-05-11 0:18 ` Firmin Martin 2021-05-07 1:46 ` Felipe Contreras 2021-05-07 8:55 ` Denton Liu 2021-05-11 1:09 ` Firmin Martin 2021-05-11 5:12 ` Felipe Contreras 2021-05-11 5:03 ` Felipe Contreras 2021-05-07 14:02 ` Sergey Organov 2021-05-11 0:46 ` Firmin Martin 2021-05-10 12:02 ` Ævar Arnfjörð Bjarmason
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=YJmmXZdwSoR+vxjw@coredump.intra.peff.net \ --to=peff@peff.net \ --cc=firminmartin24@gmail.com \ --cc=git@vger.kernel.org \ --cc=gitster@pobox.com \ --cc=johannes.schindelin@gmail.com \ --cc=kusmabite@gmail.com \ --cc=liu.denton@gmail.com \ --subject='Re: [PATCH v1 1/8] compat/terminal: let prompt accept input from pipe' \ /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
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).