git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Azeem Bande-Ali <me@azeemba.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Azeem Bande-Ali via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org, David Barr <b@rr-dav.id.au>
Subject: Re: [PATCH] help.c: help.autocorrect=prompt waits for user action
Date: Fri, 13 Aug 2021 22:57:39 -0400	[thread overview]
Message-ID: <CABye916n=EuKU3u2ybNtmT8Te9y0C__NsPR7Vdj9LKrf-y9coQ@mail.gmail.com> (raw)
In-Reply-To: <4f72cd3d-bcc7-a9b0-cc11-f0d7c5650365@gmail.com>

On Thu, Aug 12, 2021 at 6:52 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> I think it's better to use bullet lists, e.g.:
>
> ```
> If git detects typos and ...
> <skip>
> ... git will try to suggest the correct command or even run the intended
> command. Possible values are:
>      - 0 (default): show the suggested command
>      - positive number: run the suggested command after specified
> deciseconds (0.1 sec).
>      - "immediate": run the suggested command immediately
>      - "prompt": show the suggestion and prompt for confirmation to run
> the command
>      - "never": don't show any suggestions nor run them
> ```

Thanks for the feedback. I agree the bullets do look much better!

  reply	other threads:[~2021-08-14  2:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11  0:15 [PATCH] help.c: help.autocorrect=prompt waits for user action Azeem Bande-Ali via GitGitGadget
2021-08-12 10:52 ` Bagas Sanjaya
2021-08-14  2:57   ` Azeem Bande-Ali [this message]
2021-08-12 19:37 ` Junio C Hamano
2021-08-14  3:07   ` Azeem Bande-Ali
2021-08-14  5:11 ` [PATCH v2] " Azeem Bande-Ali via GitGitGadget
2021-08-14  5:50   ` Bagas Sanjaya
2021-08-14 18:20   ` Junio C Hamano
2021-08-14 18:40     ` Azeem Bande-Ali
2021-08-16 12:28     ` Johannes Schindelin
2021-08-15  1:50   ` [PATCH v3] " Azeem Bande-Ali via GitGitGadget
2021-09-08  0:18     ` 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

  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='CABye916n=EuKU3u2ybNtmT8Te9y0C__NsPR7Vdj9LKrf-y9coQ@mail.gmail.com' \
    --to=me@azeemba.com \
    --cc=b@rr-dav.id.au \
    --cc=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@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).