unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Severe lossage from unread-command-events
Date: Thu, 06 Aug 2015 20:47:33 +0200	[thread overview]
Message-ID: <871tfgl0e2.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87k2t831gf.fsf@fencepost.gnu.org> (David Kastrup's message of "Thu, 06 Aug 2015 17:01:52 +0200")

David Kastrup <dak@gnu.org> writes:

> Well, according to how I read the variable description of
> unread-command-events, some are bounced back there from input which has
> already been recorded.  The description reads:
>
>     Documentation:
>     List of events to be read as the command input.
>     These events are processed first, before actual keyboard input.
>     Events read from this list are not normally added to ‘this-command-keys’,
>     as they will already have been added once as they were read for the
>     first time.
>     An element of the form (t . EVENT) forces EVENT to be added to that list.
>
> My test programs used (t . EVENT) after just using EVENT did not do the
> trick either.

Uh oh.  This is bad news for macro recording of list events.

Defining kbd macro...
Auto-saving...done
<t> is undefined

and the "<t> is undefined" message comes with an abort of macro
recording.  Quite the nuisance.  So  I'll remove the t thing again and
will see how I fare then.

Now obviously if my events appear first in unread-command-events, they
cannot already have been added to this-command-keys, but at least list
events apparently must not be added in the (t . EVENT) form or
_something_ will attempt a lookup and fail.

Since the message appears only _once_, it would appear that the problem
stops occuring the moment macro recording by C-x ( has stopped.

What a can of worms.

-- 
David Kastrup



  parent reply	other threads:[~2015-08-06 18:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 15:46 Severe lossage from unread-command-events David Kastrup
2015-08-06 14:29 ` Eli Zaretskii
2015-08-06 15:01   ` David Kastrup
2015-08-06 15:25     ` Eli Zaretskii
2015-08-06 15:46       ` David Kastrup
2015-08-06 16:21         ` Eli Zaretskii
2015-08-07 16:08       ` Stefan Monnier
2015-08-07 16:41         ` David Kastrup
2015-08-08 15:14           ` raman
2015-08-07 18:13         ` Eli Zaretskii
2015-08-06 15:33     ` David Kastrup
2015-08-06 16:10       ` Eli Zaretskii
2015-08-06 16:16         ` David Kastrup
2015-08-06 18:47     ` David Kastrup [this message]
2015-08-06 20:00       ` David Kastrup
2015-08-10 16:56         ` David Kastrup
2015-08-10 17:35           ` Eli Zaretskii
2015-08-10 17:47             ` David Kastrup
2015-08-10 18:17               ` Eli Zaretskii
2015-08-10 18:34                 ` David Kastrup

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=871tfgl0e2.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=eliz@gnu.org \
    --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).