From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 13299@debbugs.gnu.org, nyc4bos@aol.com
Subject: bug#13299: 24.3.50; Tramp adb and device not found
Date: Mon, 18 Mar 2013 19:26:55 +0200 [thread overview]
Message-ID: <83vc8o1uw0.fsf@gnu.org> (raw)
In-Reply-To: <8738vt88n4.fsf@gmx.de>
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: nyc4bos@aol.com, 13299@debbugs.gnu.org
> Date: Mon, 18 Mar 2013 08:33:19 +0100
>
> > What do you mean by "timer" here? Even in Emacs this has multiple
> > meanings, to say nothing of the rest of the world ;-)
>
> There is the following code:
>
> (with-timeout (10)
> (with-temp-buffer
> (when (zerop (call-process tramp-adb-program nil t nil "devices"))
> ...
>
> No problem under GNU/Linux. Under MS Windows, the timeout does not
> interrupt the `call-process' form, when it is overdued. That's why I
> have replaced it with a `start-process' implementation.
Hmm... can you describe how this works on Posix platforms? Once
call-process forks the child process, it is AFAICS blocked inside
waitpid, so how do Emacs timers (which are the basis for with-timeout)
succeed to run at all? What am I missing?
next prev parent reply other threads:[~2013-03-18 17:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87han5s0dv.fsf@gmx.de>
2012-12-31 12:24 ` bug#13299: 24.3.50; Tramp adb and device not found Jürgen Hötzel
2012-12-31 15:32 ` Michael Albinus
2012-12-28 21:28 ` nyc4bos
2013-01-05 20:26 ` nyc4bos
2013-01-07 9:59 ` Michael Albinus
2013-01-26 5:57 ` nyc4bos
2013-02-04 14:38 ` Michael Albinus
2013-02-05 23:32 ` nyc4bos
2013-02-27 9:25 ` Michael Albinus
2013-03-05 21:43 ` nyc4bos
2013-03-09 21:14 ` nyc4bos
2013-03-11 10:27 ` Michael Albinus
2013-03-16 20:00 ` nyc4bos
2013-03-17 17:31 ` Michael Albinus
2013-03-17 18:34 ` Eli Zaretskii
2013-03-18 7:33 ` Michael Albinus
2013-03-18 17:26 ` Eli Zaretskii [this message]
2013-03-18 17:36 ` Michael Albinus
2013-03-21 22:47 ` nyc4bos
2013-03-23 11:57 ` Michael Albinus
2013-01-06 18:25 ` Jürgen Hötzel
2013-01-07 21:10 ` nyc4bos
2013-01-07 23:55 ` nyc4bos
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=83vc8o1uw0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13299@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=nyc4bos@aol.com \
/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).