From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: some accept-process-output races fixed; Tramp FIXMEs
Date: Tue, 22 Jan 2019 19:58:05 +0100 [thread overview]
Message-ID: <87y37ctt8i.fsf@gmx.de> (raw)
In-Reply-To: <83womw8wcc.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 22 Jan 2019 18:56:35 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
>> At least this was the case 15+ years ago, and also supporting XEmacs. If
>> we could guarantee that (accept-process-output p) returns when either
>> output has arrived and or the process has finished, I could change the
>> code. This promise must be kept for all Emacs versions since 24, and for
>> all platforms, including w32.
>
> I don't know about XEmacs (is that still a concern in Tramp?), but in
> Emacs you can poll a process for output with accept-process-output
> like this:
>
> (accept-process-output PROC 0)
>
> AFAICT, this worked in Emacs 24.1 as well.
XEmacs has gone for Tramp, two years ago. I will check whether this
works for Tramp, but it must wait a little bit. These days I'm concerned
about the smb method. Recent smbclient, with all combinations of
SMB1/SMB2/SMB3 protocol versions, client and server, is a disaster for
Tramp. I must puzzle this out, somehow.
After that, I will see what I can do with accept-process-output.
Avoiding timeouts promises speedup. Let's see.
Best regards, Michael.
next prev parent reply other threads:[~2019-01-22 18:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 18:33 some accept-process-output races fixed; Tramp FIXMEs Paul Eggert
2019-01-16 8:32 ` Michael Albinus
2019-01-16 8:38 ` Paul Eggert
2019-01-16 8:49 ` Michael Albinus
2019-01-16 13:03 ` Michael Albinus
2019-01-16 13:25 ` Stefan Monnier
2019-01-16 18:39 ` Paul Eggert
2019-01-16 19:07 ` Stefan Monnier
2019-01-17 0:15 ` Paul Eggert
2019-01-20 9:57 ` Michael Albinus
2019-01-21 23:02 ` Daniel Colascione
2019-01-22 16:54 ` Eli Zaretskii
2019-01-22 7:09 ` Paul Eggert
2019-01-22 16:56 ` Eli Zaretskii
2019-01-22 18:58 ` Michael Albinus [this message]
2019-01-22 22:06 ` Stefan Monnier
2019-01-22 22:45 ` Michael Albinus
2019-01-23 16:18 ` Eli Zaretskii
2019-01-23 18:35 ` Michael Albinus
2019-01-23 22:19 ` Daniel Pittman
2019-01-23 16:47 ` Stefan Monnier
2019-01-23 17:36 ` Paul Eggert
2019-01-28 15:37 ` Michael Albinus
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=87y37ctt8i.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).