Windows named sockets

--0000000000005d89e505ed25498d
Content-Type: text/plain; charset="UTF-8"

Hello all,
I am not entirely sure if this is the correct place to ask, but here goes.
I was trying to replicate my emacs configuration to Windows and I noticed
that the daemon support on Windows is different i.e you cannot use named
sockets.

Then I found this bug
https://lists.gnu.org/archive/html/bug-gnu-emacs/2015-01/msg00814.html that
describes the implementation and that the reason for not having named
sockets on Windows is that filesystem sockets are not supported.

However since a certain Windows version that is available
https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/  .

So my question is - is this something planned or was it decided against it?

Best regards,
Nikoleta Misheva

--0000000000005d89e505ed25498d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div>Hello all, <br></div>I am no=
t entirely sure if this is the correct place to ask, but here goes. I was t=
rying to replicate my emacs configuration to Windows and I noticed that the=
 daemon support on Windows is different i.e you cannot use named sockets. <=
br><br></div>Then I found this bug <a href=3D"https://lists.gnu.org/archive=
/html/bug-gnu-emacs/2015-01/msg00814.html">https://lists.gnu.org/archive/ht=
ml/bug-gnu-emacs/2015-01/msg00814.html</a> that describes the implementatio=
n and that the reason for not having named sockets on Windows is that files=
ystem sockets are not supported. <br><br></div>However since a certain Wind=
ows version that is available <a href=3D"https://devblogs.microsoft.com/com=
mandline/af_unix-comes-to-windows/">https://devblogs.microsoft.com/commandl=
ine/af_unix-comes-to-windows/</a>=C2=A0 .<br><br></div>So my question is - =
is this something planned or was it decided against it?<br><br></div>Best r=
egards,<br></div>Nikoleta Misheva<br></div>

--0000000000005d89e505ed25498d--