unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Leo <sdl.web@gmail.com>
Cc: Bug-Gnu-Emacs <bug-gnu-emacs@gnu.org>, emacs-devel@gnu.org
Subject: Re: emacs server with X11 build on OSX
Date: Mon, 2 Aug 2010 22:22:05 +0200	[thread overview]
Message-ID: <AANLkTimhcz87DykX5dgDx7WXYNecpEoKgsB+0zzSOxr_@mail.gmail.com> (raw)
In-Reply-To: <m162ztuhyf.fsf@cam.ac.uk>

(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?

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.

    Juanma



=== modified file 'lisp/server.el'
--- lisp/server.el	2010-05-29 23:50:47 +0000
+++ lisp/server.el	2010-08-02 20:16:16 +0000
@@ -564,5 +564,5 @@
 		       ;; The other args depend on the kind of socket used.
 		       (if server-use-tcp
-			   (list :family nil
+			   (list :family 'ipv4
 				 :service t
 				 :host (or server-host 'local)



  reply	other threads:[~2010-08-02 20:22 UTC|newest]

Thread overview: 24+ 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 [this message]
2010-08-03  2:12       ` Ken Raeburn
2010-08-03  2:47         ` Juanma Barranquero
2010-08-03  5:01           ` Leo
2010-08-03 12:02             ` Juanma Barranquero
2010-08-03 12:44               ` Andreas Schwab
2010-08-03 12:48                 ` Juanma Barranquero
2010-08-03 13:01                   ` Andreas Schwab
2010-08-03 13:03                     ` Juanma Barranquero
2010-08-04  0:52                       ` YAMAMOTO Mitsuharu
2010-08-04 15:25                         ` bug#6781: " Chong Yidong
2010-09-25  3:57                           ` YAMAMOTO Mitsuharu
2010-09-27 12:12                             ` Juanma Barranquero
2010-08-04 13:18           ` Stefan Monnier
2010-08-05  9:02             ` Juanma Barranquero
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                     ` Juanma Barranquero
2010-09-24 19:38                     ` bug#6781: " Juanma Barranquero
2010-09-24 22:27                       ` 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

  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=AANLkTimhcz87DykX5dgDx7WXYNecpEoKgsB+0zzSOxr_@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 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).