From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: wrglin@gmail.com, 38079@debbugs.gnu.org
Subject: bug#38079: On Windows tramp hangs after server-start is called
Date: Fri, 08 Nov 2019 12:34:22 +0200 [thread overview]
Message-ID: <83k18ad5ch.fsf@gnu.org> (raw)
In-Reply-To: <87sgmyvm9d.fsf@gmx.de> (message from Michael Albinus on Fri, 08 Nov 2019 08:51:42 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Wanrong Lin <wrglin@gmail.com>, 38079@debbugs.gnu.org
> Date: Fri, 08 Nov 2019 08:51:42 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> But I don't understand the underlying difficulty to ensure
> >> system-name never changes.
> >
> > There are two system calls that return this information on Windows,
> > and they treat the letter-case differently. The second system call
> > needs the winsock layer to be initialized, and we don't want to do
> > that at startup because it causes various problems (sorry, I no longer
> > remember the details of that part). So we only call the network-aware
> > system call after some network connection is available.
>
> Shouldn't we document this in etc/PROBLEMS?
What would you suggest to document? This is an internal detail of the
Emacs implementation, and users have no control on the results. Maybe
I'm missing something, but what useful workarounds can we suggest?
next prev parent reply other threads:[~2019-11-08 10:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 0:52 bug#38079: On Windows tramp hangs after server-start is called Wanrong Lin
2019-11-06 16:06 ` Eli Zaretskii
2019-11-06 16:14 ` martin rudalics
2019-11-06 17:37 ` Michael Albinus
2019-11-06 16:50 ` Wanrong Lin
2019-11-06 18:11 ` Eli Zaretskii
2019-11-08 7:51 ` Michael Albinus
2019-11-08 10:34 ` Eli Zaretskii [this message]
2019-11-08 10:50 ` Michael Albinus
2019-11-08 13:35 ` Eli Zaretskii
2019-11-07 15:23 ` Michael Albinus
2019-11-07 16:18 ` Wanrong Lin
2019-11-07 17:45 ` Michael Albinus
2019-11-07 16:18 ` Wanrong Lin
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=83k18ad5ch.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38079@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=wrglin@gmail.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).