From: D. Goel <deego@glue.umd.edu>
Subject: unread-command-events always nil?
Date: 28 Sep 2002 02:18:25 -0400 [thread overview]
Message-ID: <87y99meixa.fsf@computer.localdomain> (raw)
unread-command-events always seems to be nil[1], both in emacs21.2 as
well as in CVS.
[1] Or am I confused using a wrong variable for trying to
access the pending events? If so, what is the right one to
use?
As an example, please look at this code below (in emacs -q
-no-site-file), Go to end, press C-x C-e, and then press some
keystrokes (rapidly). Wait 6 seconds, for emacs to output the 2 lines
unread-command-events. Both of them have their first field as nil
(though there were clearly inputs pending when they were outputted..).
(progn
(discard-input)
(sleep-for 3)
(insert
(format "%S,%S,%S" unread-command-events last-input-event
(input-pending-p)))
(sleep-for 3)
(insert
(format "\n%s,%S,%S" unread-command-events last-input-event
(input-pending-p))))
In GNU Emacs 21.2.1 (i386-debian-linux-gnu, X toolkit, Xaw3d scroll
bars) of 2002-03-22 on raven, modified by Debian configured using
`configure i386-debian-linux-gnu --prefix=/usr
--sharedstatedir=/var/lib --libexecdir=/usr/lib
--localstatedir=/var/lib --infodir=/usr/share/info
--mandir=/usr/share/man --with-pop=yes --with-x=yes
--with-x-toolkit=athena --without-gif' Important settings: value of
$LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: value of
$LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC:
nil value of $LC_TIME: nil value of $LANG: C locale-coding-system:
nil default-enable-multibyte-characters: t
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
Recent input:
M-x g n u s <return> M-x r e p o r t - e m a c s -
b u g <return>
Recent messages:
Opening nnfolder server on DEEGO...
No new newsgroups
Checking new news...
Opening nnfolder server on archive...
Opening nndraft server...
Checking new news...done
Loading emacsbug...done
reply other threads:[~2002-09-28 6:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87y99meixa.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.
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).