GNU bug report logs - #20675
24.3; emacsclient cannot talk to emacs

Previous Next

Full log

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Bruce Korb <bruce.korb <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3; emacsclient cannot talk to emacs
Date: Wed, 27 May 2015 11:09:26 -0700

From: Bruce Korb <bruce.korb <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3; emacsclient cannot talk to emacs
--text follows this line--
This bug report will be sent to the Bug-GNU-Emacs mailing list
and the GNU bug tracker at debbugs.gnu.org.  Please check that
the From: line contains a valid email address.  After a delay of up
to one day, you should receive an acknowledgment at that address.

Please write in English if possible, as the Emacs maintainers
usually do not have translators for other languages.

Please describe exactly what actions triggered the bug, and
the precise symptoms of the bug.  If you can, give a recipe
starting from `emacs -Q':

I have no idea what may have triggered the bug.
I am using emacsclient and emacs just fine for quite a while,
then all of a sudden:

> $ emacsclient cscope.files
> emacsclient: can't find socket; have you started the server?
> To start the server in Emacs, type "M-x server-start".
> emacsclient: No socket or alternate editor.  Please use:
>
>         --socket-name
>         --server-file      (or environment variable EMACS_SERVER_FILE)
>         --alternate-editor (or environment variable ALTERNATE_EDITOR)

so I start up another xterm running bash and everything is fine.
For a while.  Then the same thing happens.  I do *NOT* have to restart
emacs or even the server code.  I have to start another xterm.
(Re-exec-ing bash does no good.)  So, clearly, something is scrogged
in the xterm so that it cannot talk to...........

AH HA!!

The problem is that I need to redirect TMPDIR to different places for
different tasks.  So that explainer above might get expanded to include
mention of the fact that this directory:  ${TMPDIR}/emacs$(id -u)
is used for communication.  I'd have found the problem long ago.

So please consider this an RFE to the above "can't find socket" message.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.