From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.help Subject: Re: how do i get the list of pending input events? Date: Mon, 30 Sep 2002 15:18:04 -0600 Sender: help-gnu-emacs-admin@gnu.org Message-ID: <3D98BF8C.2040808@ihs.com> References: <87smzspqbj.fsf@computer.localdomain> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1033421176 12379 127.0.0.1 (30 Sep 2002 21:26:16 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 30 Sep 2002 21:26:16 +0000 (UTC) Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 17w83S-0003DV-00 for ; Mon, 30 Sep 2002 23:26:15 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 17w83h-00051B-00; Mon, 30 Sep 2002 17:26:29 -0400 Original-Path: shelby.stanford.edu!nntp.stanford.edu!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!193.174.75.178!news-fra1.dfn.de!fu-berlin.de!uni-berlin.de!170.207.51.80!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 12 Original-NNTP-Posting-Host: 170.207.51.80 Original-X-Trace: fu-berlin.de 1033420681 12951672 170.207.51.80 (16 [82742]) User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 X-Accept-Language: en-us Original-Xref: nntp.stanford.edu gnu.emacs.help:105560 Original-To: help-gnu-emacs@gnu.org Errors-To: help-gnu-emacs-admin@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.help:2104 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:2104 D. Goel wrote: > In elisp, how do i get the list of pending input events? > > I couldn't find it in the manual or anywhere else till now. :( AFAIK, the variable `unread-command-events'. -- Kevin Rodgers