Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bob Wilson <bwilson@tensilica.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] edit documentation for TUI mode
Date: Fri, 11 May 2007 17:58:00 -0000	[thread overview]
Message-ID: <uirazfdjd.fsf@gnu.org> (raw)
In-Reply-To: <46423A94.2090607@tensilica.com> (message from Bob Wilson on Wed, 	09 May 2007 14:18:12 -0700)

> Date: Wed, 09 May 2007 14:18:12 -0700
> From: Bob Wilson <bwilson@tensilica.com>
> 
> I noticed that the TUI-related sections of the GDB docs are a little rough.  I'm 
> no expert on this feature, but I thought I'd have a go at cleaning up the docs 
> anyway.  I discovered a few minor discrepancies between the current behavior and 
> the document, along with numerous issues of style, formatting and grammar. 
> Here's what I came up with.  Is it OK?

Thanks!  This is approved, provided that you take care of a couple
minor comments below:

> +@pindex @value{GDBTUI}
> +The TUI mode is enabled by default when you invoke @value{GDBN} as
> +either @samp{@value{GDBTUI}} or @samp{@value{GDBP} -tui}.
> +You can also switch in and out of TUI mode while @value{GDBN} runs.

The last sentence begs a question: ``how''?  We should either answer
that right there, or have an xref to where the appropriate command is
described.

> -@table @key
> +@table @asis
>  @kindex PgUp
> -@item PgUp
> +@item @key{PgUp}
>  Scroll the active window one page up.

Why did you switch to `@table @asis' and an explicit @key in each
item?  What was wrong with the previous method?


  reply	other threads:[~2007-05-11 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 21:18 Bob Wilson
2007-05-11 17:58 ` Eli Zaretskii [this message]
2007-05-11 18:30   ` Bob Wilson
2007-05-12  7:19     ` Eli Zaretskii
2007-05-14 17:54       ` Bob Wilson

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=uirazfdjd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bwilson@tensilica.com \
    --cc=gdb-patches@sources.redhat.com \
    /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