From: Ken Raeburn <raeburn@raeburn.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Bug-Gnu-Emacs <bug-gnu-emacs@gnu.org>, Leo <sdl.web@gmail.com>,
emacs-devel@gnu.org
Subject: Re: emacs server with X11 build on OSX
Date: Mon, 2 Aug 2010 22:12:29 -0400 [thread overview]
Message-ID: <83F33443-0C3F-4F9B-B584-D9301250B8FC@raeburn.org> (raw)
In-Reply-To: <AANLkTimhcz87DykX5dgDx7WXYNecpEoKgsB+0zzSOxr_@mail.gmail.com>
On Aug 2, 2010, at 16:22, Juanma Barranquero wrote:
> (I'm Cc:ing this to bug-gnu-emacs to create a bug report.)
>
> On Mon, Aug 2, 2010 at 17:56, Leo <sdl.web@gmail.com> wrote:
>
>>> (make-network-process :name "server" :server t :family nil :service t
>>> :host 'local)
>
>> I have used the following in server-start as workaround:
>>
>> (make-network-process :name "server" :server t :family 'ipv4 :service t)
>
> If ":family 'ipv4" works and ":family nil" does not, that surely means
> that Emacs is chosing ipv6. Does server.el work with the attached
> patch?
There was one more difference, which was that your suggestion included ":host 'local" and his workaround did not.
Using ":host 'local" causes the C code to look up the name "localhost", which may or may not map to IPv4 and/or IPv6 addresses. (Almost always an IPv4 address of 127.0.0.1; sometimes IPv6 also, and I've occasionally seen it mapped to the local ethernet interface's IPv4 address.) Not specifying the host at all causes a wildcard address to be used, which would be reachable from other hosts, whereas 127.0.0.1 generally is not. (Actually, in the version I'm looking at, which isn't quite current, it causes INADDR_ANY to be used, which looks like a bug if the address family is not specifically given as AF_INET. I'll try to look at that a little closer if I get some time next weekend.)
> I don't know whether that means that your system is set up only for
> ipv6, or that it has both ipv6 and ipv4 and make-network-process is
> selecting ipv6 for `localhost'. In any case, server.el / emacsclient.c
> are not adapted to ipv6, so forcing ipv4 seems right for the moment
> being.
Yes.
Ken
next prev parent reply other threads:[~2010-08-03 2:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 19:17 emacs server with X11 build on OSX Leo
2010-08-02 14:57 ` Juanma Barranquero
2010-08-02 15:56 ` Leo
2010-08-02 20:22 ` Juanma Barranquero
2010-08-02 22:16 ` bug#6781: " Leo
2010-08-03 2:12 ` Ken Raeburn [this message]
2010-08-03 2:47 ` Juanma Barranquero
2010-08-03 2:47 ` Juanma Barranquero
2010-08-03 5:01 ` Leo
2010-08-03 12:02 ` bug#6781: " Juanma Barranquero
2010-08-03 12:02 ` Juanma Barranquero
2010-08-03 12:44 ` bug#6781: " Andreas Schwab
2010-08-03 12:44 ` Andreas Schwab
2010-08-03 12:48 ` Juanma Barranquero
2010-08-03 13:01 ` bug#6781: " Andreas Schwab
2010-08-03 13:01 ` Andreas Schwab
2010-08-03 13:03 ` bug#6781: " Juanma Barranquero
2010-08-03 13:03 ` Juanma Barranquero
2010-08-04 0:52 ` bug#6781: " YAMAMOTO Mitsuharu
2010-08-04 0:52 ` YAMAMOTO Mitsuharu
2010-08-04 15:25 ` bug#6781: " Chong Yidong
2010-08-04 15:25 ` Chong Yidong
2010-09-25 3:57 ` YAMAMOTO Mitsuharu
2010-09-27 12:12 ` Juanma Barranquero
2010-09-27 12:12 ` Juanma Barranquero
2010-09-25 3:57 ` YAMAMOTO Mitsuharu
2010-08-03 12:48 ` Juanma Barranquero
2010-08-03 5:01 ` Leo
2010-08-04 13:18 ` Stefan Monnier
2010-08-05 9:02 ` Juanma Barranquero
2010-08-09 11:24 ` bug#6781: " Stefan Monnier
2010-08-09 11:24 ` Stefan Monnier
2010-08-09 17:08 ` Juanma Barranquero
2010-08-10 13:31 ` Stefan Monnier
2010-08-10 18:31 ` bug#6781: " Juanma Barranquero
2010-08-10 18:31 ` Juanma Barranquero
2010-09-24 19:38 ` bug#6781: " Juanma Barranquero
2010-09-24 22:27 ` Stefan Monnier
2010-09-24 22:27 ` Stefan Monnier
2010-09-24 19:38 ` Juanma Barranquero
2010-08-10 13:31 ` Stefan Monnier
2010-08-09 17:08 ` Juanma Barranquero
2010-08-05 9:02 ` Juanma Barranquero
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=83F33443-0C3F-4F9B-B584-D9301250B8FC@raeburn.org \
--to=raeburn@raeburn.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=sdl.web@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 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.