unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Revamping sit-for [Was: Lingering input pending with motif menu bar]
Date: Sat, 08 Jul 2006 11:31:28 -0400	[thread overview]
Message-ID: <E1FzEmG-0004gN-LK@fencepost.gnu.org> (raw)
In-Reply-To: <87mzbl3wrd.fsf@stupidchicken.com> (message from Chong Yidong on Fri, 07 Jul 2006 17:55:50 -0400)

    Richard has said he wanted to replace sit-for so that only actual
    Emacs Lisp events will interrupt input.

I would like to do this, but first we need to check whether there are
any callers that really want the current behavior of sit-for.  It's
unlikely that any caller does want it, but not impossible, and we
should check.

Could people please check?

  parent reply	other threads:[~2006-07-08 15:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-01 23:55 [simon.marshall@misys.com: Lingering input pending with motif menu bar] Richard Stallman
2006-07-04  1:13 ` Chong Yidong
2006-07-04  9:08   ` Kim F. Storm
2006-07-04 13:45     ` Chong Yidong
2006-07-04 20:53       ` Richard Stallman
2006-07-04 21:21         ` [simon.marshall@misys.com: Lingering input pending with motifmenu bar] Drew Adams
2006-07-05 17:01           ` Richard Stallman
2006-07-05 20:48             ` [simon.marshall@misys.com: Lingering input pending withmotifmenu bar] Drew Adams
2006-07-07  4:14               ` Richard Stallman
2006-07-05 17:01           ` [simon.marshall@misys.com: Lingering input pending with motifmenu bar] Richard Stallman
2006-07-05  0:06         ` [simon.marshall@misys.com: Lingering input pending with motif menu bar] Chong Yidong
2006-07-05  9:04           ` Kim F. Storm
2006-07-04 17:03     ` [simon.marshall@misys.com: Lingering input pending with motifmenu bar] Drew Adams
2006-07-07 21:55 ` Revamping sit-for [Was: Lingering input pending with motif menu bar] Chong Yidong
2006-07-07 22:02   ` Revamping sit-for David Kastrup
2006-07-07 22:58   ` Revamping sit-for [Was: Lingering input pending with motif menu bar] Drew Adams
2006-07-08  1:39     ` Revamping sit-for Chong Yidong
2006-07-08  3:53       ` Drew Adams
2006-07-08 12:00         ` Chong Yidong
2006-07-08 12:36           ` David Kastrup
2006-07-08 12:56             ` Romain Francoise
2006-07-08 12:40           ` Stefan Monnier
2006-07-08 15:41           ` Drew Adams
2006-07-08 20:57           ` Richard Stallman
2006-07-08 15:31   ` Richard Stallman [this message]
2006-07-08 22:49     ` Revamping sit-for [Was: Lingering input pending with motif menu bar] Kim F. Storm
2006-07-09 19:03       ` Richard Stallman
2006-07-10 12:10         ` Kim F. Storm
2006-07-11  5:50           ` Richard Stallman
2006-07-08 23:02     ` Kim F. Storm
2006-07-10 19:47     ` Revamping sit-for Chong Yidong
2006-07-11  0:24       ` Chong Yidong
2006-07-11 18:16         ` Richard Stallman
2006-07-11 18:39           ` Kim F. Storm
2006-07-12 19:22             ` Richard Stallman

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=E1FzEmG-0004gN-LK@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).