all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Deal gracefully with up-events (Bug#19746)
Date: Tue, 11 Aug 2015 07:01:49 +0200	[thread overview]
Message-ID: <87vbcme7uq.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvk2t2iz6q.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 10 Aug 2015 17:58:41 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> * keyboard.c (apply_modifiers_uncached, parse_solitary_modifier)
>> (parse_modifiers_uncached): React gracefully to "up-" modifiers:
>> those may easily be injected by user-level Lisp code.
>> (read_key_sequence): Discard unbound up-events like unbound
>> down-events: they are even more likely only relevant for special
>> purposes.
>
> Looks good.
>
>> While Emacs will not produce up-events on its own currently (those are
>> converted to drag or click events before being converted to
>> Lisp-readable structures), the input queue can be made to contain them
>> by synthesizing events to `unread-command-events'.  Emacs should deal
>> consistently with such events.
>
> This probably belongs in a comment rather than in the ChangeLog.

Well, the information is in there, just written differently.  And "on
its own currently" is correct in the commit message but might become
wrong in a comment eventually.

-- 
David Kastrup



  reply	other threads:[~2015-08-11  5:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 13:59 (unknown) David Kastrup
2015-08-10 13:59 ` [PATCH] Deal gracefully with up-events (Bug#19746) David Kastrup
2015-08-10 21:58   ` Stefan Monnier
2015-08-11  5:01     ` David Kastrup [this message]
2015-08-10 14:02 ` (unknown) 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vbcme7uq.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.