Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Stephane Carrez <stcarrez@nerim.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Provide TUI fast key action with specific readline keymap
Date: Sat, 31 Aug 2002 22:40:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1020901072938.24946F-100000@is> (raw)
In-Reply-To: <3D70FD20.6020409@nerim.fr>


On Sat, 31 Aug 2002, Stephane Carrez wrote:

> > Thanks for working on this, but you never responded to my request to
> > change the manual accordingly.  I really don't think we should have
> > first-class user-level features that are not documented.
> 
> I agree with you; I responded and I sent the following patch few days ago:
> 
> [RFC]: Document TUI breakpoints and SingleKey mode
> 	http://sources.redhat.com/ml/gdb-patches/2002-08/msg00907.html

Sorry, I somehow missed that.

Those patches are approved with the following comments:

  - "@table @emph" is IMHO not a good idea for markers, since @emph is 
    typeset in a slanted font in the printed manual.  I suggest to use 
    "@table code" instead.

  - In the description of the SingleKey keybindings, please make the 
    index entries indicate that those are SingleKey bindings, like this:

    @kindex c@r{, SingleKey TUI key}

    Otherwise, the user looking at the index will not be able to 
    distinguish between, say, the entry for the normal GDB `c' (continue) 
    command and the SingleKey binding of `c'.

Thanks!


  reply	other threads:[~2002-09-01  5:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-31  5:34 Stephane Carrez
2002-08-31  8:30 ` Eli Zaretskii
2002-08-31  9:59   ` Stephane Carrez
2002-08-31 22:40     ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-25 15:25 Stephane Carrez
2002-08-26  8:55 ` 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=Pine.SUN.3.91.1020901072938.24946F-100000@is \
    --to=eliz@is.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