public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "amerey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/29582] Usability improvement: CTRL+C when debugindod client is downloading a file
Date: Thu, 29 Sep 2022 02:23:21 +0000	[thread overview]
Message-ID: <bug-29582-4717-xq7RGb3Lyu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29582-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29582

--- Comment #8 from Aaron Merey <amerey at redhat dot com> ---
(In reply to Tom de Vries from comment #7)
> Created attachment 14367 [details]
> tentative patch

Thanks for the patch, I think this works nicely. I just have a couple
suggestions regarding some of the wording. 

> +      if (debuginfod_cancel == debuginfod_ask)
> +	{
> +	  int resp = nquery (_("Cancel further downloading for this session? "));
> +	  if (resp)
> +	    debuginfod_cancel = debuginfod_all;
> +	  else
> +	    debuginfod_cancel = debuginfod_one;
> +	}
> +      if (debuginfod_cancel == debuginfod_all)
> +	{
> +	  gdb_printf (_("Debuginfod has been disabled.\n"));

Here it could be useful to include instructions for how to re-enable
debuginfod. Something like: 
"Debuginfod has been disabled. To re-enable use the 'set debuginfod enabled on'
command."

> +  add_setshow_enum_cmd ("cancel", class_run, debuginfod_cancel_enum,
> +			_("Set cancellation mode for debuginfod."),
> +			_("Show cancellation mode for debuginfod."),
> +			_("\
> +When set to one, ^C cancels a single download.\n\
> +When set to all, ^C cancels all further downloads.\n\
> +When set to ask, ^C asks what to do."),

To be extra clear about what the cancellation mode is I'd add the following
line:

The cancellation mode controls the behavior of ^C while a file is downloading
from debuginfod.\n\
When set to one, ^C cancels a single download.\n\
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-09-29  2:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18  8:20 [Bug cli/29582] New: " mliska at suse dot cz
2022-09-18  8:34 ` [Bug cli/29582] " vries at gcc dot gnu.org
2022-09-20 11:28 ` vries at gcc dot gnu.org
2022-09-20 13:59 ` vries at gcc dot gnu.org
2022-09-20 15:36 ` mliska at suse dot cz
2022-09-22  0:16 ` amerey at redhat dot com
2022-09-28 15:09 ` vries at gcc dot gnu.org
2022-09-28 15:09 ` vries at gcc dot gnu.org
2022-09-29  2:23 ` amerey at redhat dot com [this message]
2022-09-29  8:26 ` vries at gcc dot gnu.org
2024-01-10 17:09 ` ssbssa at sourceware dot org
2024-02-22 22:28 ` amerey at redhat dot com

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=bug-29582-4717-xq7RGb3Lyu@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).