public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Merey <amerey@redhat.com>
Cc: gdb-patches@sourceware.org, pedro@palves.net, tdevries@suse.de,
	mliska@suse.cz
Subject: Re: [PATCH v2] [gdb/debuginfod] Ask to cancel further downloads
Date: Sat, 17 Dec 2022 10:23:03 +0200	[thread overview]
Message-ID: <83edsyigm0.fsf@gnu.org> (raw)
In-Reply-To: <20221217001525.82647-1-amerey@redhat.com> (message from Aaron Merey via Gdb-patches on Fri, 16 Dec 2022 19:15:25 -0500)

> Cc: pedro@palves.net, tdevries@suse.de, Aaron Merey <amerey@redhat.com>,
>  Martin Liška <mliska@suse.cz>
> Date: Fri, 16 Dec 2022 19:15:25 -0500
> From: Aaron Merey via Gdb-patches <gdb-patches@sourceware.org>
> 
> +  add_setshow_enum_cmd ("cancel", class_run, debuginfod_cancel_enum,
> +			_("Set cancellation mode for debuginfod."),

I suggest a more specific wording here:

  Set cancellation mode for debuginfod downloads.

> +			_("Show cancellation mode for debuginfod."),

And similarly here.

> +The cancellation mode modifies the behavior of ^C while a file is downloading\
> + from debuginfod.\nWhen set to one, two ^C cancels a single download.\n\
> +When set to all, two ^C cancels all further downloads.\n\
> +When set to ask, two ^C asks what to do.\nA single ^C during downloading is\
> + passed to the target process being debugged.\nA second ^C during downloading\
> + may raise a prompt asking whether to cancel the download or send ^C to the\
> + target.\nIf the download is to be cancelled, the cancellation mode takes\
> + effect and no ^C is sent to the target."),

This should use "cancel" and "ask", in plural, not "cancels" and
"asks" in singular, because it talks about "two ^C".

However, it might be better to say

  ..., pressing ^C twice cancels a single download

and similarly for the other instances, because "two ^C" is somewhat
awkward.  That is the wording you used for the manual, and it is
better.

> +@kindex set debuginfod cancel
> +@anchor{set debuginfod cancel}
> +@item set debuginfod cancel
> +@itemx set debuginfod cancel one
> +@cindex debuginfod cancellation mode
> +Pressing @code{^C} twice during downloading will cancel the current

I suggest to use @kbd{Ctrl-C} instead @code{^C}, here and elsewhere in
the patch.

> +@item set debuginfod cancel all
> +Pressing @code{^C} twice during downloading will cancel all further
> +downloads.

I think "this and all further downloads" is more accurate.

> +@item set debuginfod cancel ask
> +Pressing @code{^C} twice during a download will prompt the user to

Instead of "the user", please use "you", or even nothing.  The manual
is written from the POV of "the user", so we should not use "the user"
as some third party.

Also, "will prompt whether to cancel", since this is the essence of
the question.  The user is not asked to cancel, the user is asked
whether GDB should cancel.

> +cancel all further downloads before attempting to perform the next query.
                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I'm not sure I understand the emphasized part.  What do you mean by
"before attempting"?

> +@kindex show debuginfod cancel
> +@item show debuginfod cancel
> +Display whether @code{debuginfod cancel} is set to @code{one}, @code{all} or
> +@code{ask}.

I suggest to reword this

  Display the current setting of @code{debuginfod cancel}.

Thanks.

  reply	other threads:[~2022-12-17  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17  0:15 Aaron Merey
2022-12-17  8:23 ` Eli Zaretskii [this message]
2022-12-21 21:47   ` Aaron Merey
2022-12-22  7:01     ` Eli Zaretskii

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=83edsyigm0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=amerey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mliska@suse.cz \
    --cc=pedro@palves.net \
    --cc=tdevries@suse.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).