From: Johannes Altmanninger <aclopte@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: kashav madan via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, kashav madan <kshvmdn@gmail.com>
Subject: Re: [PATCH] help: add space after autocorrect prompt
Date: Thu, 16 Dec 2021 07:27:09 +0100 [thread overview]
Message-ID: <20211216062709.b4tcagi6qcqhasrh@gmail.com> (raw)
In-Reply-To: <xmqqh7b933ej.fsf@gitster.g>
On Wed, Dec 15, 2021 at 02:32:36PM -0800, Junio C Hamano wrote:
> "kashav madan via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> > From: Kashav Madan <kshvmdn@gmail.com>
> >
> > Signed-off-by: Kashav Madan <kshvmdn@gmail.com>
> > ---
> > help: add space after autocorrect prompt
>
> The patch looks OK-ish, but let's make sure. We will find what we
> should write in the log message while doing so.
>
> If you look at the output from
>
> $ git grep -C2 git_prompt \*.c
>
> you'll notice that existing message given to git_prompt look like
> these:
>
> yesno = git_prompt(_("Are you sure [Y/n]? "), PROMPT_ECHO);
>
> yesno = git_prompt(_("Do you want me to do it for you "
> "[Y/n]? "), PROMPT_ECHO);
>
> strbuf_addf(&msg, _("Run '%s' instead? (y/N)"), assumed);
> answer = git_prompt(msg.buf, PROMPT_ECHO);
>
> The last one is what you are touching in this patch.
>
> There is another one in credential.c that asks not just a single
> yes/no answer, so it is justifiably different from all the others,
> but the one you noticed is different from what we see above in three
> points:
>
> - It does not leave a SP before where the end-user input goes;
> - It append (y/N) _after_ question mark;
I actually prefer this one;
Run 'status' instead? [y/N]
sounds better than
Run 'status' instead [y/N]?
but that's not a strong opinion.
next prev parent reply other threads:[~2021-12-16 6:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 21:41 [PATCH] help: add space after autocorrect prompt kashav madan via GitGitGadget
2021-12-15 22:32 ` Junio C Hamano
2021-12-16 6:27 ` Johannes Altmanninger [this message]
2021-12-16 15:55 ` Eric Sunshine
2021-12-16 21:32 ` Junio C Hamano
2021-12-15 22:58 ` [PATCH v2] help: make auto-correction prompt more consistent kashav madan via GitGitGadget
2021-12-16 3:12 ` Junio C Hamano
2021-12-16 18:18 ` [PATCH v3 0/4] normalize format of yes/no prompts kashav madan via GitGitGadget
2021-12-16 18:18 ` [PATCH v3 1/4] bisect--helper: normalize format string " Kashav Madan via GitGitGadget
2021-12-16 21:39 ` Junio C Hamano
2021-12-16 21:49 ` Junio C Hamano
2021-12-16 18:18 ` [PATCH v3 2/4] clean: normalize format string of yes/no prompt Kashav Madan via GitGitGadget
2021-12-16 18:18 ` [PATCH v3 3/4] add-patch: " Kashav Madan via GitGitGadget
2021-12-16 18:18 ` [PATCH v3 4/4] help: make auto-correction prompt more consistent Kashav Madan via GitGitGadget
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211216062709.b4tcagi6qcqhasrh@gmail.com \
--to=aclopte@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
--cc=kshvmdn@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).