From: storm@cua.dk (Kim F. Storm)
Cc: monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: while-no-input
Date: 06 Oct 2002 00:43:45 +0200 [thread overview]
Message-ID: <5xlm5cmrq6.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <E17x61m-0004mr-00@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> That is not very useful if inside this body you use library
> functions that take a long time to complete, such as file-operations
> that dispatch to ange-ftp:
>
> It doesn't seem like a terribly important case to worry about.
For users of ido or icomplete as well as ange-ftp (or tramp?),
it is definitely a nuisance; I believe that the number of users
affected by this from time to time is fairly high.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-10-05 22:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 21:19 while-no-input Stefan Monnier
2002-10-02 19:24 ` while-no-input Richard Stallman
2002-10-02 21:43 ` while-no-input Stefan Monnier
2002-10-03 13:28 ` while-no-input Richard Stallman
2002-10-03 15:53 ` while-no-input Stefan Monnier
2002-10-03 22:44 ` while-no-input Kim F. Storm
2002-10-03 22:33 ` while-no-input Stefan Monnier
2002-10-04 15:46 ` while-no-input Richard Stallman
2002-10-04 15:59 ` while-no-input Stefan Monnier
2002-10-05 16:33 ` while-no-input Richard Stallman
2002-10-24 0:06 ` while-no-input Kim F. Storm
2002-10-24 7:20 ` while-no-input Stefan Monnier
2002-10-24 10:24 ` while-no-input Kim F. Storm
2002-10-25 5:35 ` while-no-input Richard Stallman
2002-10-25 9:19 ` while-no-input Kim F. Storm
2002-10-26 20:15 ` while-no-input Richard Stallman
2002-10-25 13:44 ` while-no-input Stefan Monnier
2002-10-26 20:13 ` while-no-input Richard Stallman
2002-10-29 19:45 ` while-no-input Stefan Monnier
2002-10-31 17:25 ` while-no-input Richard Stallman
2002-10-31 18:03 ` while-no-input Stefan Monnier
2002-11-02 3:32 ` while-no-input Richard Stallman
2002-11-02 4:07 ` last try (was: while-no-input) Stefan Monnier
2002-11-03 1:04 ` Kim F. Storm
2002-11-04 12:01 ` Richard Stallman
2002-11-03 13:57 ` Richard Stallman
2002-11-04 14:55 ` Stefan Monnier
2002-11-04 23:53 ` Kim F. Storm
2002-11-06 4:50 ` Richard Stallman
2002-11-06 9:45 ` Kim F. Storm
2002-11-06 17:51 ` last try Kai Großjohann
2002-11-07 15:09 ` Richard Stallman
2002-11-07 15:07 ` last try (was: while-no-input) Richard Stallman
2002-10-05 22:43 ` Kim F. Storm [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-26 9:26 AW: vc-state always calls heuristic function klaus.berndl
2004-11-26 11:44 ` Kim F. Storm
2004-11-27 18:51 ` while-no-input Richard Stallman
2004-11-27 23:03 ` while-no-input Kim F. Storm
2004-11-29 6:11 ` while-no-input Richard Stallman
2004-11-29 14:20 ` while-no-input Stefan Monnier
2004-11-30 7:03 ` while-no-input Richard Stallman
2004-11-30 14:56 ` while-no-input Kim F. Storm
2004-11-29 14:30 while-no-input klaus.berndl
2004-11-29 14:55 ` while-no-input Stefan Monnier
2004-11-29 15:02 while-no-input klaus.berndl
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=5xlm5cmrq6.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.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).