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: Mon, 10 Aug 2015 19:47:06 +0200	[thread overview]
Message-ID: <87d1yvf339.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83fv3roxlf.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 10 Aug 2015 20:35:40 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: David Kastrup <dak@gnu.org>
>> Cc: emacs-devel@gnu.org
>> Date: Mon, 10 Aug 2015 18:56:42 +0200
>> 
>> David Kastrup <dak@gnu.org> writes:
>> 
>> > Looks like I can (and must) leave off the (cons t ...) for my use
>> > case.  I haven't seen any bad effects from doing so: events are looked
>> > up in keymaps and recorded just fine so far.  I don't know what the
>> > implications of the t thing are.  But other than that, things do look
>> > good so far.
>> 
>> Any chance for this patch going in anytime soon?  Anything I should be
>> doing here?
>
> I was waiting for you to tell whether it solves all the problems you
> know about with pushing events onto unread-command-events.  If you are
> satisfied by what you see after applying the patch, I will push.

So far the results looked good.  I suspect that it does nothing about
the "escaping e" problem of Artur.  And I suspect that the "(cons t"
feature will (still?) not work reliably.  However, neither of those
problems would appear to be caused by your patch, so there seems little
point in delaying that patch.

-- 
David Kastrup



  reply	other threads:[~2015-08-10 17: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
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 [this message]
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=87d1yvf339.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).