From: "Eli Zaretskii" <eliz@elta.co.il>
To: Stephane Carrez <stcarrez@nerim.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Document tui reg commands
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <6480-Sat13Mar2004182210+0200-eliz@elta.co.il> (raw)
In-Reply-To: <405318FE.8000904@nerim.fr> (message from Stephane Carrez on Sat, 13 Mar 2004 15:21:50 +0100)
> Date: Sat, 13 Mar 2004 15:21:50 +0100
> From: Stephane Carrez <stcarrez@nerim.fr>
>
> This is the documentation part of the new TUI reg commands.
Thanks.
> Ok to commit?
Yes, but please fix the following small gotchas:
> +@item tui reg float
> +@kindex tui reg float
> +Show the floating point registers in the register window.
> +
> +@item tui reg general
> +@kindex tui reg general
> +Show the general registers in the register window.
> +
> +@item tui reg next
> +@kindex tui reg next
There's no need to make a @kindex entry for all the 3 variants of this
command; a single "@kindex tui reg" will do. In general, it's not
useful to have several index entries that all begin with the same
string and all point to the same page, because that doesn't add any
information to someone who is looking through the index.
> + [...] The predefined register groups are the
> +following: @code{general}, @code{float}, @code{system}, @code{vector},
> +@code{all}, @code{save}, @code{restore}.
> +
> +@item tui reg system
> +@kindex tui reg system
> +Show the system registers in the register window.
I think we should have a description of at least some of these
predefined register groups. For example, I could probably easily
guess what "reg float" or "reg vector" mean, but I have no idea about
"reg system" or "reg save/restore". I'm afraid a description such as
"Show the system registers in the register window." doesn't help me to
unlock this mystery.
WARNING: multiple messages have this Message-ID
From: "Eli Zaretskii" <eliz@elta.co.il>
To: Stephane Carrez <stcarrez@nerim.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Document tui reg commands
Date: Sat, 13 Mar 2004 16:23:00 -0000 [thread overview]
Message-ID: <6480-Sat13Mar2004182210+0200-eliz@elta.co.il> (raw)
Message-ID: <20040313162300.5faNZangdDF5FRJy6NR7-WxEaMP5bXuQmMrf7LN3s5E@z> (raw)
In-Reply-To: <405318FE.8000904@nerim.fr> (message from Stephane Carrez on Sat, 13 Mar 2004 15:21:50 +0100)
> Date: Sat, 13 Mar 2004 15:21:50 +0100
> From: Stephane Carrez <stcarrez@nerim.fr>
>
> This is the documentation part of the new TUI reg commands.
Thanks.
> Ok to commit?
Yes, but please fix the following small gotchas:
> +@item tui reg float
> +@kindex tui reg float
> +Show the floating point registers in the register window.
> +
> +@item tui reg general
> +@kindex tui reg general
> +Show the general registers in the register window.
> +
> +@item tui reg next
> +@kindex tui reg next
There's no need to make a @kindex entry for all the 3 variants of this
command; a single "@kindex tui reg" will do. In general, it's not
useful to have several index entries that all begin with the same
string and all point to the same page, because that doesn't add any
information to someone who is looking through the index.
> + [...] The predefined register groups are the
> +following: @code{general}, @code{float}, @code{system}, @code{vector},
> +@code{all}, @code{save}, @code{restore}.
> +
> +@item tui reg system
> +@kindex tui reg system
> +Show the system registers in the register window.
I think we should have a description of at least some of these
predefined register groups. For example, I could probably easily
guess what "reg float" or "reg vector" mean, but I have no idea about
"reg system" or "reg save/restore". I'm afraid a description such as
"Show the system registers in the register window." doesn't help me to
unlock this mystery.
next prev parent reply other threads:[~2004-03-13 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Stephane Carrez
2004-03-13 14:21 ` Stephane Carrez
2004-03-19 0:09 ` Eli Zaretskii [this message]
2004-03-13 16:23 ` Eli Zaretskii
2004-03-28 12:32 ` Stephane Carrez
2004-03-28 13:40 ` 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=6480-Sat13Mar2004182210+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=stcarrez@nerim.fr \
/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