From: storm@cua.dk (Kim F. Storm)
Cc: storm@cua.dk
Subject: Re: Emacs manual desribes keyboard macros in the wrong section.
Date: 27 Feb 2003 12:10:20 +0100 [thread overview]
Message-ID: <5x65r6q8rn.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200302261901.NAA03553@moose.dms.auburn.edu>
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Kim Storm wrote:
>
> The keyboard macro feature is currently described under customizations
> (in custom.texi), but IMO keyboard macros are not customizations
> (unless you name them etc. which I believe is not the typical use of
> keyboard macros). In my experience, the typical use of keyboard
> macros is for doing repeated editing similar to "search and replace".
>
> In my opinion it would certainly be appropriate to give keyboard
> macros their own chapter once their discussion has reached an
> appropriate size. They are important enough to motivate that.
> ... most Emacs users are not Elisp programmers. For
> somebody who does not know Elisp, keyboard macros are an important
> customization and extension tool.
I agree, and moving it out of the customization chapter which talks
about variables and other "lisp-like" stuff will probably make more
non-Elisp programmers aware of it.
> Keyboard macros used as such tend
> to get named and saved in .emacs.
I could still add directions to the section on .emacs to describe how
one can save keyboard macros in .emacs (either as named commands or
as key bindings).
next prev parent reply other threads:[~2003-02-27 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 16:32 Emacs manual desribes keyboard macros in the wrong section Kim F. Storm
2003-02-26 19:01 ` Luc Teirlinck
2003-02-27 11:10 ` Kim F. Storm [this message]
2003-02-27 22:30 ` Richard Stallman
2003-02-28 12:46 ` Kim F. Storm
2003-02-28 13:36 ` Robert J. Chassell
2003-03-01 21:44 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5x65r6q8rn.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.