Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCHv3 3/3] WIP: disable progress bars setting
Date: Tue, 16 Dec 2025 10:05:27 +0000	[thread overview]
Message-ID: <87wm2m4u8o.fsf@redhat.com> (raw)
In-Reply-To: <8b7e71ed-3139-442e-b46d-d96c18e8351b@suse.de>

Tom de Vries <tdevries@suse.de> writes:

> On 12/5/25 8:53 PM, Andrew Burgess wrote:
>> +file from debuginfod.  When @value{off}, @value{GDBN} will not display
>> +a progress bar.  When @value{on}, @value{GDBN} will display a progress
>
> Hi,
>
> I noticed in the build:
> ...
> gdb.texinfo:51356: warning: undefined flag: off
> gdb.texinfo:51357: warning: undefined flag: on
> ...
> and indeed in the online documentation:
> ...
> set progress-bars enabled [on|off]
>
>      Set whether GDB can display a progress bar when downloading a file 
> from debuginfod. When {No value for ‘off’}, GDB will not display a 
> progress bar. When {No value for ‘on’}, GDB will display a progress bar 
> if GDB’s output console supports it.
> ...

Sorry for that.  I pushed the patch below to resolve this problem.

Thanks,
Andrew

--

commit 9529188a184f69d804c9c1c974c51d3b3460e676
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Tue Dec 16 10:00:38 2025 +0000

    gdb/doc: fix incorrect use of @value
    
    In commit:
    
      commit 255a9c42709958d0925d1d0d1d39d262972fd2a6
      Date:   Fri Dec 5 11:33:29 2025 +0000
    
          gdb: new setting to disable progress bars
    
    I incorrectly used @value{on} and @value{off} to reference the on/off
    settings of a new flag.  This caused the following warnings when
    building the docs:
    
      gdb.texinfo:51356: warning: undefined flag: off
      gdb.texinfo:51357: warning: undefined flag: on
    
    Looking through the docs there seems to be a split, in some cases we
    use @code and in others we use @samp.  I'm not sure @code is correct,
    so I've switched to use @samp.  The warnings are gone after this
    patch.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 4c012393ff4..f77fe17c81f 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -51353,8 +51353,8 @@ Debuginfod Settings
 @cindex progress bars, disabling
 @item set progress-bars enabled @r{[}on@r{|}off@r{]}
 Set whether @value{GDBN} can display a progress bar when downloading a
-file from debuginfod.  When @value{off}, @value{GDBN} will not display
-a progress bar.  When @value{on}, @value{GDBN} will display a progress
+file from debuginfod.  When @samp{off}, @value{GDBN} will not display
+a progress bar.  When @samp{on}, @value{GDBN} will display a progress
 bar if @value{GDBN}'s output console supports it.
 
 @kindex show progress-bars enabled


      reply	other threads:[~2025-12-16 10:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 16:38 [PATCH 0/4] Fixes and tests related to new boxed hint startup text Andrew Burgess
2025-12-04 16:38 ` [PATCH 1/4] gdb: remove some unnecessary code from print_gdb_hints Andrew Burgess
2025-12-04 17:14   ` Patrick Monnerat
2025-12-04 16:38 ` [PATCH 2/4] gdb: small white space fix in print_gdb_hints Andrew Burgess
2025-12-04 16:38 ` [PATCH 3/4] gdb: make get_chars_per_line return an unsigned value Andrew Burgess
2025-12-04 16:38 ` [PATCH 4/4] gdb: fix crashes and weird output from new boxed hint text Andrew Burgess
2025-12-04 19:02 ` [PATCH 0/4] Fixes and tests related to new boxed hint startup text Guinevere Larsen
2025-12-04 19:32   ` Andrew Burgess
2025-12-04 19:47 ` [PATCH 0/2] " Andrew Burgess
2025-12-04 19:47   ` [PATCH 1/2] gdb: make get_chars_per_line return an unsigned value Andrew Burgess
2025-12-04 19:47   ` [PATCH 2/2] gdb: fix crashes and weird output from new boxed hint text Andrew Burgess
2025-12-05  7:06     ` Eli Zaretskii
2025-12-05 10:17       ` Andrew Burgess
2025-12-05 11:19         ` Eli Zaretskii
2025-12-05 19:53   ` [PATCHv3 0/3] Fixes and tests related to new boxed hint startup text Andrew Burgess
2025-12-05 19:53     ` [PATCHv3 1/3] gdb: make get_chars_per_line return an unsigned value Andrew Burgess
2025-12-10 16:48       ` Tom Tromey
2025-12-05 19:53     ` [PATCHv3 2/3] gdb: fix crashes and weird output from new boxed hint text Andrew Burgess
2025-12-10 16:51       ` Tom Tromey
2025-12-05 19:53     ` [PATCHv3 3/3] WIP: disable progress bars setting Andrew Burgess
2025-12-06  9:12       ` Eli Zaretskii
2025-12-09 17:32       ` Andrew Burgess
2025-12-10 16:55         ` Tom Tromey
2025-12-15 15:33           ` Andrew Burgess
2025-12-16  7:40       ` Tom de Vries
2025-12-16 10:05         ` Andrew Burgess [this message]

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=87wm2m4u8o.fsf@redhat.com \
    --to=aburgess@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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