From: D. Goel <deego@glue.umd.edu>
Subject: Re: how do i get the list of pending input events?
Date: 30 Sep 2002 21:59:05 -0400 [thread overview]
Message-ID: <87lm5i7wd2.fsf@computer.localdomain> (raw)
In-Reply-To: 3D98BF8C.2040808@ihs.com
Kevin Rodgers <kevinr@ihs.com> writes:
>
> AFAIK, the variable `unread-command-events'.
Have been looking into it more and asking for more help around.
(thanks to RMS, i now understand that-->
It seems there's no way to get a list of pending events for a lisp
program though I think there really should be.
unread-command-events only contains events that have been put by lisp
programs into it. Otherwise `unread-comand-events' seems to always
contain nil.
DG http://24.197.159.102/~deego/
--
next prev parent reply other threads:[~2002-10-01 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 19:07 how do i get the list of pending input events? D. Goel
2002-09-30 21:18 ` Kevin Rodgers
2002-10-01 1:59 ` D. Goel [this message]
2002-10-01 3:13 ` Evgeny Roubinchtein
2002-10-01 14:53 ` Stefan Monnier <foo@acm.com>
2002-10-03 16:57 ` D. Goel
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=87lm5i7wd2.fsf@computer.localdomain \
--to=deego@glue.umd.edu \
/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.
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).