[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#35238: 27.0.50; Clarify eventp behaviour with booleans
From: |
Stefan Monnier |
Subject: |
bug#35238: 27.0.50; Clarify eventp behaviour with booleans |
Date: |
Thu, 11 Apr 2019 19:42:46 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
> As mentioned in a past commit[1], nil is not an event.
> Since the car of a mouse click event is considered its type,
> shouldn't (nil) also be rejected as an event?
Not sure it's worth the trouble (there are already lots of other objects
that aren't events but for which eventp returns non-nil).
> Should t be counted as an event?
>
> (eventp t) ; => t
> (eventp '(t)) ; => t
Not sure if we ever generate such an event, but what would be the
benefit of rejecting it?
Stefan
- bug#35238: 27.0.50; Clarify eventp behaviour with booleans, Basil L. Contovounesios, 2019/04/11
- bug#35238: 27.0.50; Clarify eventp behaviour with booleans,
Stefan Monnier <=
- bug#35238: 27.0.50; Clarify eventp behaviour with booleans, Basil L. Contovounesios, 2019/04/12
- bug#35238: 27.0.50; Clarify eventp behaviour with booleans, Stefan Monnier, 2019/04/12
- bug#35238: 27.0.50; Clarify eventp behaviour with booleans, Eli Zaretskii, 2019/04/12
- bug#35238: 27.0.50; Clarify eventp behaviour with booleans, Basil L. Contovounesios, 2019/04/13
- bug#35238: 27.0.50; Clarify eventp behaviour with booleans, Stefan Monnier, 2019/04/13
- bug#35238: 27.0.50; Clarify eventp behaviour with booleans, Basil L. Contovounesios, 2019/04/22
- bug#35238: 27.0.50; Clarify eventp behaviour with booleans, Stefan Monnier, 2019/04/22