From: Eli Zaretskii <eliz@gnu.org>
To: Bob Wilson <bwilson@tensilica.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [doc/commit] Re: fix use of @kbd and @key in gdb.texinfo
Date: Tue, 17 Oct 2006 19:47:00 -0000 [thread overview]
Message-ID: <upscqrage.fsf@gnu.org> (raw)
In-Reply-To: <4533C78B.10800@tensilica.com> (message from Bob Wilson on Mon, 16 Oct 2006 10:55:23 -0700)
> Date: Mon, 16 Oct 2006 10:55:23 -0700
> From: Bob Wilson <bwilson@tensilica.com>
> CC: gdb-patches@sources.redhat.com
>
> Somehow the message that Eli sent directly to me did not get through, probably
> lost in a torrent of spam, and I don't read gdb-patches regularly. That's not a
> very good excuse, though -- I should have made a point of checking the list in
> case anyone had issues with my change. I'm sorry.
No sweat.
> What about the TUI chapter? There are lots of "C-" prefixes in there and it's
> not tied to Emacs users. Should they all use "Ctrl-"?
I left "C-" there because the text mentions the corresponding Emacs
keybindings. But I'm open to other opinions.
> Also, I noticed that there is a mix of upper- and lowercase for Ctrl key
> combinations, e.g, "Ctrl-C" vs. "Ctrl-c". Can we make them all the same?
The latter should be used in @kbd, the former in @samp. If this is
so, it's deliberate: @kbd shows what one types, @samp shows what's
displayed on the screen as the result. AFAIK, you always get Ctrl-C
(uppercase C) when you interrupt a process.
> Here is a patch to fix one more place to use "Ctrl-". It was using "C-d" before
> my change, but it seems like it ought to use "Ctrl-" to be consistent, since it
> has nothing to do with Emacs.
Right, please commit this. Thanks.
next prev parent reply other threads:[~2006-10-17 19:47 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 [this message]
2006-10-17 21:18 ` Bob Wilson
2006-10-24 17:52 ` Jim Blandy
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=upscqrage.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