unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Peter Dyballa <Peter_Dyballa@Web.DE>,
	emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: Sensible menu bindings
Date: Tue, 29 Mar 2005 12:31:00 +0200	[thread overview]
Message-ID: <x5y8c6wxp7.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3fyyeyegr.fsf_-_@kfs-l.imdomain.dk> (Kim F. Storm's message of "Tue, 29 Mar 2005 11:43:32 +0200")

storm@cua.dk (Kim F. Storm) writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> I recently suggested patches to report menu bindings using the real
>>> menu item texts rather than the internal names, like this:
>>
>>>       File=>Print=>Print With Faces
>>
>> I agree it would be an improvement.  But IIRC you did it by
>> modifying key-description, which also applies to things like C-h c
>> where I think it's important to keep a representation that can be
>> passed directly to `kbd'.
>
> How do you copy/paste the output from C-h c?  From *Messages* buffer?
>
> With C-h k, you get a buffer from which you can copy the original menu
> binding -- and with my patch, that binding is still shown for C-h k
> (see example below).
>
>> So I'd recommend to add an arg to key-description and then only use
>> it at those places where it makes sense (basically, for the keys
>> returned by `where-is').
>
> With my patch, (key-description KEY t) will do just that.
> Making C-h c using that is trivial (I already did so).
>
> Anyway, Richard don't think this is an improvement, so
> unless more people speak up, it's a dead end.

I think it is an improvement since we are talking here mainly about
user-level instead of programmer-accessible documentation.  With
regard to the duplication of information: how feasible would it be to
make kbd accept File=>Print=>Print With Faces strings?  Then there
would be no necessity to report a different form.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-03-29 10:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <91a0b1e20a73068697a422453a2dcb7e@Web.DE>
     [not found] ` <01c53211$Blat.v2.4$99a09d00@zahav.net.il>
     [not found]   ` <m34qevh0ag.fsf@kfs-l.imdomain.dk>
     [not found]     ` <m1u0mvnxlj.fsf-monnier+emacs@gnu.org>
2005-03-29  9:43       ` Sensible menu bindings (was Re: A doc typo?) Kim F. Storm
2005-03-29 10:31         ` David Kastrup [this message]
2005-03-29 11:41           ` Sensible menu bindings Kim F. Storm
2005-03-29 13:45         ` Stefan Monnier
2005-03-29 14:58           ` Kim F. Storm

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x5y8c6wxp7.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=Peter_Dyballa@Web.DE \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).