From xemacs-m  Wed Feb 26 02:19:26 1997
Received: from maes.esrin.esa.it (maes.esrin.esa.it [192.106.252.50])
	by xemacs.org (8.8.5/8.8.5) with SMTP id CAA13502
	for <xemacs-beta@xemacs.org>; Wed, 26 Feb 1997 02:19:23 -0600 (CST)
Received: from mail.esrin.esa.it (plod.esrin.esa.it) by maes.esrin.esa.it with SMTP id AA23983
  (5.65c/IDA-1.4.4 for <xemacs-beta@xemacs.org>); Wed, 26 Feb 1997 09:19:22 +0100
Received: from penelope.esa.it by mail.esrin.esa.it (4.1/SMI-4.1)
	id AA23503; Wed, 26 Feb 97 08:19:24 GMT
Date: Wed, 26 Feb 97 08:19:24 GMT
Message-Id: <9702260819.AA23503@mail.esrin.esa.it>
Received: by penelope.esa.it (4.1/SMI-4.1)
	id AA15692; Wed, 26 Feb 97 09:24:05 +0100
From: Simon Marshall <Simon.Marshall@esrin.esa.it>
To: XEmacs Beta <xemacs-beta@xemacs.org>
In-Reply-To: <m2k9nw7e2e.fsf@altair.xemacs.org> (message from Steven L Baur on
	25 Feb 1997 13:47:53 -0800)
Subject: Re: [19.15b95]: input-pending-p is nil even after keypress
Reply-To: Simon Marshall <Simon.Marshall@esrin.esa.it>

>> It seems that input-pending-p returns nil even after a simple keypress:

>> xemacs -no-init-file -no-site-file
>> (progn (loop for fubar from 1 to 10000 by 1) (input-pending-p)) C-j C-p
>> => nil

>> Which is wrong.  If I replace the loop with (sit-for 5) or add (sit-for
>> 5) before or after the loop, then the value is t.

sb> I can't duplicate this (after raising the loop count to something that
sb> gives sufficient delay) in 20.0, 20.1-b3 or 19.15-b96.

Uh-uh.  I found this particular problem after one of the lazy-lock.el cpu
comments by Sudeep Palat.  Sudeep, can you reproduce the above problem?
Raise the loop value if you can't type the C-p fast enough.  I guess you
will reproduce it, but what is your configuration?  Here's mine:

Configured for `sparc-sun-sunos4.1.3C'.

  What operating system and machine description files should XEmacs use?
        `s/sunos4-1-3-shr.h' and `m/sparc.h'
  What compiler should XEmacs be built with?              gcc -g -O2 -pipe
  Should XEmacs use the GNU version of malloc?            yes
  Should XEmacs use the relocating allocator for buffers? yes
  What window system should XEmacs use?                   x11
  Compiling in support for XAUTH.
  Compiling in support for XPM.
  Compiling in support for GIF image conversion.
  Compiling in support for DBM.
  Using the Lucid menubar.
  Using the Lucid scrollbar.
  Using the Motif dialog boxes.
  Compiling in extra code for debugging.

With gcc-2.7.2 and x11r5.28.  Maybe I'll build with cc and then we can
start the blame-gcc-loop again.

