From: storm@cua.dk (Kim F. Storm)
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
bkey1@tampabay.rr.com, emacs-devel@gnu.org
Subject: Re: server-start under Windows
Date: 08 Nov 2002 15:53:38 +0100 [thread overview]
Message-ID: <5x8z04p0y5.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <m24raumpqa.fsf@nyaumo.btinternet.com>
Jason Rumney <jasonr@gnu.org> writes:
> "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:
>
> > I only wrote server.el which uses make-network-process.
> > You'll need to hack process.c like you did for emacsclient.c to make
> > it understand `local' connections (I assume that w32 has unix-domain
> > sockets of some sort).
>
> It doesn't, which makes me wonder how much hacking went into
> emacsclient.c, or maybe it will also start failing once the server
> side is working.
I foun this in the patch to emacsclient.c -- it seems to assume
that AF_UNIX is supported (but just not documented)?! That may
be true, but it seems questionalbe to me...
--- _21.3/lib-src/emacsclient.c 2002-09-30 20:45:30.000000000 -0400
+++ 21.3/lib-src/emacsclient.c 2002-11-06 23:47:58.000000000 -0500
@@ -40,7 +40,18 @@
#else
# include <pwd.h>
#endif /* not VMS */
-
+#ifdef WINDOWSNT
+# include <errno.h>
+# include <fcntl.h>
+ extern int _execvp (const char*, char* const*);
+# ifndef HAVE_STRUCT_SOCKADDR_UN
+ struct sockaddr_un
+ {
+ short int sun_family; /* AF_UNIX */
+ char sun_path[108]; /* path name (gag) */
+ };
+# endif
+#endif
char *getenv (), *getwd ();
char *getcwd ();
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-11-08 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 14:34 server-start under Windows bkey1
2002-11-06 15:55 ` Stefan Monnier
2002-11-06 20:02 ` Jason Rumney
2002-11-08 14:53 ` Kim F. Storm [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 20:01 bkey1
2002-11-07 14:49 ` Stefan Monnier
2002-11-06 4:45 Ben Key
2002-11-06 9:53 ` Kim F. Storm
2002-11-06 15:45 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5x8z04p0y5.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=bkey1@tampabay.rr.com \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.