From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jonathan Ganc <jonoftexas@gmail.com>
Cc: 9356-done@debbugs.gnu.org
Subject: bug#9356: `event-modifiers' documentation
Date: Tue, 30 Aug 2011 10:51:38 -0400 [thread overview]
Message-ID: <jwvy5yb6jx4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4E55133E.1030308@gmail.com> (Jonathan Ganc's message of "Wed, 24 Aug 2011 10:05:34 -0500")
> Does that qualify, though? I'm not sure what the desired behavior for
> mouse-10 would be but, for example, (event-modifiers 'mouse-9) => (click)
> and I certainly don't have a mouse-9 button.
If you ever manage to get a mouse-10 event, it should (and will) be
labeled as a click. I've slightly changed the docstring to reflect the
fact that only `click' may be missing (and that this can not only
result in a nil result, e.g. C-mouse-10 will only say (control) instead
of (control click)).
Stefan
> On 08/24/2011 09:27 AM, Stefan Monnier wrote:
>>> The documentation for `event-modifiers' states:
>>> "If EVENT is a symbol that has never been used in an event that has been
>>> read as input in the current Emacs session, then this function can return
>>> nil, even when EVENT actually has modifiers." However, looking in the
>>> event-modifier' definition, the function
>>> internal-event-symbol-parse-modifiers' seems to deal with this (potential)
>>> issue. Can someone give me an example where `event-modifier' would
>>> inappropriately return nil?
>> (event-modifiers 'mouse-1) => (click)
>> (event-modifiers 'mouse-10) => nil
>>
>> Not sure if other modifiers than `click' can be missing.
>>
>>
>> Stefan
>>
>>
prev parent reply other threads:[~2011-08-30 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 5:46 bug#9356: `event-modifiers' documentation Jonathan Ganc
2011-08-24 14:27 ` Stefan Monnier
[not found] ` <4E55133E.1030308@gmail.com>
2011-08-30 14:51 ` Stefan Monnier [this message]
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=jwvy5yb6jx4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9356-done@debbugs.gnu.org \
--cc=jonoftexas@gmail.com \
/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.