unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Roland Winkler <Roland.Winkler@physik.uni-erlangen.de>
Cc: emacs-devel@gnu.org, rms@gnu.org,
	Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: Re: `special' keys in keyboard macros
Date: Thu, 16 Oct 2003 12:18:30 +0200	[thread overview]
Message-ID: <16270.28790.644900.539286@tfkp07.physik.uni-erlangen.de> (raw)
In-Reply-To: <m3ekxeqjhu.fsf@kfs-l.imdomain.dk>

On     Oct 15 2003 Kim F. Storm wrote:
> Richard Stallman <rms@gnu.org> writes:
> 
> >     Another possibility is to record commands names instead of keys.
> > 
> > That is possible, but I tend to think it is the wrong approach.
> 
> I agree.  
> 
> For example, it is not sufficient to record just commands names for
> commands like self-insert-command and digit-argument which make no
> sense "out of context".

I think it would be neat to have some better support for converting
"dirty", quickly hacked keyboard macros into "clean" elisp commands.
The command edit-kbd-macro gives some idea how the keys are
translated into commands. But for more complex keyboard macros (such
as those using recursive edit during execution of the macro) it will
be rather tricky to provide an automated mechanism for converting
keyboard macros into elisp commands. Up to now, I do not even have
an idea what kind of new features might be useful to support such a
conversion.

In any case, it appears to me that this is a rather different issue
than what I addressed in the bug report.

Roland

  reply	other threads:[~2003-10-16 10:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16257.16532.727889.658851@tfkp07.physik.uni-erlangen.de>
2003-10-11  5:37 ` `special' keys in keyboard macros Richard Stallman
2003-10-14 21:21   ` Stefan Monnier
2003-10-15 20:00     ` Richard Stallman
2003-10-15 21:27       ` Kim F. Storm
2003-10-16 10:18         ` Roland Winkler [this message]
2003-10-16 12:36           ` Robert J. Chassell
2003-10-16 23:07           ` 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=16270.28790.644900.539286@tfkp07.physik.uni-erlangen.de \
    --to=roland.winkler@physik.uni-erlangen.de \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=rms@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).