unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: D. Goel <deego@glue.umd.edu>
Subject: Re: how do i get the list of pending input events?
Date: 03 Oct 2002 12:57:06 -0400	[thread overview]
Message-ID: <871y77zcil.fsf@computer.localdomain> (raw)
In-Reply-To: 5lu1k6jjms.fsf@rum.cs.yale.edu

"Stefan Monnier <foo@acm.com>" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu> writes:

> >>>>> "Evgeny" == Evgeny Roubinchtein <zhenya@freeshell.org> writes:
> > Could you explain in more detail how you envision this feature?  You
> > seem to imply there is some queue which the C code does not expose to
> > the Lisp engine, and I am not sure that such queue exists.  Do you
> > have evidence to the contrary?
> 
> The queue definitely exists (called something like keybuf in the C code)
> and is not exposed to Lisp.  But the question remains: what for ?


I guess I might have been trying the wrong approach for the problem I
am having.  Perhaps peopel could sugegst alternatives---


The problem is (and I know several people have mentioned the same
problem) ---> Want to make (sit-for) ignore certain inpuuts (and
continue doing its thing as if the input never happened).  An example
of this is:

idle-timer tasks in emacs keep working fine in emacs -nw when I switch
to another window, or move my mouse to another window, or switch to
another sawfish-viewport. --- becasuse emacs -nw does not care for
mouse-events. 

But, the idle-timer stops in "regular" 'emacs', as soon as you move to
another window----(even though switching to another window is when the
user wants emacs to think it is idle and do its "idle" stuff..) [1] 



The only workaround i envisioned is to implement my own "sit-for" that
would essentially "sleep-for" for small times, and then check whether
any "real" (vix. non-mouse) event has occurred, else will continue
another sleep-fo.. and so on, until its entire sit-for-duratino is
completed.  

please write in with alternative suggestions? 

guess you could always flame me for trying ungodly things with what is
suppposed to be an editor... :)... OTOH, emacs is now an editing
environment even officially.. and of course, an OS unofficially :)



[1] <you knew the plug was coming> An example of this is the vel.el i
posted to g.e.s (or the mouse-based mvel.el i will post soon) --- say,
I want to leave my emacs scrolling up slowly, and want to work in the
adjacent applicatino while emacs is scrolling.  I can do that just
fine in emacs -nw.  But in emacs, the moment I press Alt-tab or
alt-left (sawfish), or try to move the mouse, the scrolling stops.







DG                                 http://24.197.159.102/~deego/
--

      reply	other threads:[~2002-10-03 16:57 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
2002-10-01  3:13     ` Evgeny Roubinchtein
2002-10-01 14:53       ` Stefan Monnier <foo@acm.com>
2002-10-03 16:57         ` D. Goel [this message]

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=871y77zcil.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).