From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: C-h k, C-h f and keyboard macros: Patch.
Date: 11 Feb 2003 14:10:42 +0100 [thread overview]
Message-ID: <5xsmuvufn1.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200302102356.RAA04775@eel.dms.auburn.edu>
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Currently, `describe-key' (usually C-h k) and `describe-function'
> (usually C-h f) produce confusing output when confronted with a
> keyboard macro.
> New C-h k output:
>
> C-c 3 runs the command ott
> which is a keyboard macro.
> It is bound to C-c 3.
> Macro: SPC one SPC two SPC three SPC
>
> Keyboard macro.
>
> In other words, we get the "readable" and the "formal" definition,
> yielding no duplication in this case.
GREAT IDEA!!
>
> An alternative to printing the `kmacro-display' output would be to
> just erase the offending line and not replace it with anything, but I
> find the `kmacro-display' output useful in situations where I do
> C-h k. The patch affects C-h f in the same way as C-h k.
The problem with using kmacro-display is that it is intended for
interactive use, so it prints the macro definition using `message'.
It is better to use format-kbd-macro directly:
Index: help-fns.el
===================================================================
RCS file: /cvsroot/emacs/emacs/lisp/help-fns.el,v
retrieving revision 1.28
diff -c -r1.28 help-fns.el
*** help-fns.el 4 Feb 2003 11:23:06 -0000 1.28
--- help-fns.el 11 Feb 2003 12:10:17 -0000
***************
*** 323,328 ****
--- 323,331 ----
function)))))
usage)
(car usage))
+ ((or (stringp def)
+ (vectorp def))
+ (format "\nMacro: %s" (format-kbd-macro def)))
(t "[Missing arglist. Please make a bug report.]")))
(terpri))
(let ((obsolete (and
next prev parent reply other threads:[~2003-02-11 13:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 23:56 C-h k, C-h f and keyboard macros: Patch Luc Teirlinck
2003-02-11 13:10 ` Kim F. Storm [this message]
2003-02-11 12:52 ` Juanma Barranquero
2003-02-11 14:13 ` Kim F. Storm
2003-02-11 14:07 ` Juanma Barranquero
2003-02-11 15:18 ` Kim F. Storm
2003-02-11 14:27 ` Juanma Barranquero
2003-02-11 15:36 ` Kim F. Storm
2003-02-11 14:47 ` Juanma Barranquero
2003-02-11 16:19 ` Stefan Monnier
2003-02-11 20:58 ` Kim F. Storm
2003-02-12 20:34 ` Richard Stallman
2003-02-13 0:16 ` Kim F. Storm
2003-02-11 16:03 ` Luc Teirlinck
2003-02-12 7:19 ` Richard Stallman
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=5xsmuvufn1.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@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).