Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Bob Wilson <bwilson@tensilica.com>,  gdb-patches@sources.redhat.com
Subject: Re: fix use of @kbd and @key in gdb.texinfo
Date: Tue, 24 Oct 2006 17:52:00 -0000	[thread overview]
Message-ID: <m31wox38ki.fsf@codesourcery.com> (raw)
In-Reply-To: <ubqojkfpu.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 10 Oct 2006 23:45:17 +0200")


Eli Zaretskii <eliz@gnu.org> writes:
> Specifically, I don't want to use the Emacs C-c notation in parts of
> the documentation that are not related to Emacs, because I fear that
> users who are not familiar with Emacs will not know what C-c means
> without explanation.  (The Emacs manual has a lengthy chapter
> explaining that, but GDB doesn't.)  So please change C-c etc. back to
> Ctrl-C form, except where Emacs is involved.

[Going through mail backlog]

Doesn't the gdb documentation incorporate the readline user
documentation?  That does include a section on the Emacs notation.  I
had thought the intention is to use the C- and M- notation across
Project GNU, but I can't find a reference for that.

We do explain M- in the manual, in the section "Command Completion".
We could do the same for C-, and then we could actually use the same
notation throughout the manual.


  parent reply	other threads:[~2006-10-24 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 18:56 Bob Wilson
2006-10-10 21:45 ` Eli Zaretskii
2006-10-15 21:33   ` [doc/commit] " Eli Zaretskii
2006-10-15 21:38     ` Daniel Jacobowitz
2006-10-16 17:55       ` Bob Wilson
2006-10-17 19:47         ` Eli Zaretskii
2006-10-17 21:18           ` Bob Wilson
2006-10-24 17:52   ` Jim Blandy [this message]
2006-10-25  4:30     ` 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=m31wox38ki.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=bwilson@tensilica.com \
    --cc=eliz@gnu.org \
    --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