From: storm@cua.dk (Kim F. Storm)
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: kmacro.texi
Date: Thu, 02 Dec 2004 15:17:21 +0100 [thread overview]
Message-ID: <m3u0r4bx8u.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1CZqj6-0007Tu-Mg@fencepost.gnu.org> (Richard Stallman's message of "Thu, 02 Dec 2004 08:10:28 -0500")
Richard Stallman <rms@gnu.org> writes:
> I am sure most users only occasionally define a keyboard macro, and
> don't have so many that they need to look at the definitions through a
> ring. Users who define keyboard macros often enough to want this
> feature are surely few in number.
>
> And C-x e e e ... already does something very similar.
> Nobody has complained about that so far.
>
> And C-u C-SPC C-SPC C-SPC ...
>
> These are much more limited--but indeed the first of them bothers me.
We could change the defaults:
(setq kmacro-repeat-no-prefix nil)
(setq kmacro-call-repeat-key nil)
Then the "non-spirit" behaviour would have to be enabled explicitly
by a user. And we wouldn't have to write a lot of new code for the
(as you say) rarely used kmacro history feature.
>
> With your proposal, I have to mess up the window layout just to rotate
> the macro ring
>
> I don't think that is a valid conclusion. Exiting this mode
> in the "usual" way could restore the old window layout.
True, it could work.
But I would prefer if we just change the defaults (and fix the docs)
as described above. Would that be ok?
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-12-02 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 4:30 kmacro.texi Luc Teirlinck
2004-11-30 9:53 ` kmacro.texi Kim F. Storm
2004-12-01 2:57 ` kmacro.texi Richard Stallman
2004-12-01 2:57 ` kmacro.texi Richard Stallman
2004-12-01 12:06 ` kmacro.texi Kim F. Storm
2004-12-02 13:10 ` kmacro.texi Richard Stallman
2004-12-02 14:17 ` Kim F. Storm [this message]
2004-12-04 2:46 ` kmacro.texi Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2004-12-03 19:42 kmacro.texi Stefan Monnier
2004-12-04 0:42 ` kmacro.texi 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3u0r4bx8u.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=teirllm@dms.auburn.edu \
/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.