>> I'd say use while-no-input but you're in a better position to make this call.
> the only thing i wanted is: An expert-estimation if while-no-input is
> a good way - or with-local-quit - if i remember right you said that this
> could easily being backported - maybe its not a really good idea to
Title: AW: Can't interrupt directory_files_internal run fromtimer-event-handler
>> With the current available elisp-tools (macos, functions etc.) ECB can run
>> these tasks only pseudo-stealthy...therefore a way to make this really
>> stealthy would be very importa
> With the current available elisp-tools (macos, functions etc.) ECB can run
> these tasks only pseudo-stealthy...therefore a way to make this really
> stealthy would be very important for ECB so users are not blocked...
> I have no preference how to achieve this (while-no-input, with-local-quit
>
In fact: ECB has some tasks which should be run really(!) stealthy, like
checking if a dir is empty, getting the VC-state of all files in a dir,
checking which files in a dir are read-only... in case of a remote host
The best way to do this and make sure it is stealthy is by running a
Title: AW: Can't interrupt directory_files_internal run fromtimer-event-handler
>> ECB encapslates ist "stealthy" tasks in a loop like:
>> (while (and (not (input-pending-p))
>> ...
>> So IMHO C-g should work
>Only if
> ECB encapslates ist "stealthy" tasks in a loop like:
> (while (and (not (input-pending-p))
> ...
> So IMHO C-g should work
Only if each iteration takes a (small) finite time. The OP's problem is
that one of the iteration doesn't terminate.
> AFAIK there is a new m
> Date: Mon, 8 Aug 2005 13:27:46 +0200
> From: <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>,
>
>
> >A combination of file-attributes (looking at the number of links) and
> >directory-files should do that, I think.
>
> Hmm, maybe i oversee something here - but when you have to call
> direc
For that reason, I think we should either document throw-on-input (and
keep its name), or [better] change while-no-input to return `quit' for
C-g, `input-pending-p' for input, and value of BODY otherwise.
This won't achieve the goal of making it possible to distinguish all
the possible
Title: AW: Can't interrupt directory_files_internal run fromtimer-event-handler
>>> There's no need to run any program just to know if a directory is
>>> empty. Emacs has primitives which will tell that directly (e.g.,
>>> file-attributes)
"Richard M. Stallman" <[EMAIL PROTECTED]> writes:
> BTW, `while-no-input' and `throw-on-input' are not documented on the
> Emacs Lisp Reference; and the docstring for `throw-on-input' is
> suboptimal:
>
> while-no-input is in the Lisp manual. throw-on-input is not for users
> to use;
On 8/6/05, Richard M. Stallman <[EMAIL PROTECTED]> wrote:
> while-no-input is in the Lisp manual.
Yes, you're right. Sorry.
> throw-on-input is not for users
> to use; perhaps we should rename it to while-no-input-throw-internal.
I agree.
--
/L/e/k/t/u
__
BTW, `while-no-input' and `throw-on-input' are not documented on the
Emacs Lisp Reference; and the docstring for `throw-on-input' is
suboptimal:
while-no-input is in the Lisp manual. throw-on-input is not for users
to use; perhaps we should rename it to while-no-input-throw-internal.
On 8/5/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> AFAIK there is a new macro in CVS named `while-no-input' (there
> was a discussion some time ago)
BTW, `while-no-input' and `throw-on-input' are not documented on the
Emacs Lisp Reference; and the docstring for `throw-on-input' is
subo
Klaus Zeitler wrote:
> The following problem occurs with CVS emacs + ECB under Solaris 5.8.
>
> While ECB performs its stealth update activities, emacs sometimes
> seems to
> hang for a long time.
> gdb shows the following function and backtrace:
>
> directory_files_internal (directory=16076323,
14 matches
Mail list logo
