Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 3/3] NEWS and documentation for / (slash) command.
Date: Sat, 13 Apr 2019 19:10:00 -0000	[thread overview]
Message-ID: <83lg0dk9gf.fsf@gnu.org> (raw)
In-Reply-To: <20190413190016.11970-4-philippe.waroquiers@skynet.be> (message	from Philippe Waroquiers on Sat, 13 Apr 2019 21:00:16 +0200)

> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Date: Sat, 13 Apr 2019 21:00:16 +0200
> 
> +* New commands
> +
> +/SETTING... COMMAND
> +  The / command temporarily changes some settings according to SETTING
> +  to run COMMAND.
     ^^^^^^^^^^^^^^
I'd say "for the duration of COMMAND" instead.

> +@cindex Settings
> +@cindex Temporarily change settings

By convention, index entries are not capitalized, to avoid problems
with sorting them alphabetically (which produces locale-dependent
results).

> +The following table gives the list of settings that the @code{/} command
> +can temporarily change.  The first column gives the letter sequence
> +identifying the setting corresponding to the command in the second column.
> +The third column gives the type of the setting, and list the different
> +possible values for the enumeration settings.  Note that the below table
> +is produced by the @code{help /} command.
> +
> +@smallexample
> +@c In the 'doc' build directory, the following can be produced by:
> +@c ../../gdb/gdb -q --nx  -ex 'set width 80' -ex 'set height 0' -ex 'help /' -ex quit |
> +@c   sed -e '1,/The temporarily changeable settings are:/d' -e ':a;s/^\( *\) /@\1/;ta' -e 's/^/@exdent /'
> +@c Maybe this could/should be automated by the doc Makefile ?
> +@exdent /Be       set backtrace past-entry       Boolean on|off
> +@exdent /Bl       set backtrace limit            Unsigned integer (0 means unlimited)

Please rewrite this as a @multitable, so that it looks good in all
formats.

Thanks.


  reply	other threads:[~2019-04-13 19:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-13 19:00 [RFA 0/3] / command : fast way to change setting(s) to run a command Philippe Waroquiers
2019-04-13 19:00 ` [RFA 2/3] Test for slash_command Philippe Waroquiers
2019-04-13 19:00 ` [RFA 1/3] / command : fast way to change setting(s), run a command, reset settings(s) Philippe Waroquiers
2019-04-14 18:20   ` Kevin Buettner
2019-04-15  7:34     ` Philippe Waroquiers
2019-04-13 19:00 ` [RFA 3/3] NEWS and documentation for / (slash) command Philippe Waroquiers
2019-04-13 19:10   ` Eli Zaretskii [this message]
2019-04-13 19:22     ` Philippe Waroquiers

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=83lg0dk9gf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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