From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 23202-done@debbugs.gnu.org, Live System User <nyc4bos@aol.com>
Subject: bug#23202: 24.5; emacsclient confusing server connection message
Date: Wed, 06 Nov 2019 01:45:37 +0100 [thread overview]
Message-ID: <87lfst6de6.fsf@marxist.se> (raw)
In-Reply-To: <874l35aitz.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Mon, 29 Jul 2019 00:35:20 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Live System User <nyc4bos@aol.com> writes:
>
>> Now, when invoking emacsclient, I get the following message:
>>
>> $ emacsclient +12:2 ~/.emacs
>> emacsclient: can't find socket; have you started the server?
>> To start the server in Emacs, type "M-x server-start".
>> Waiting for Emacs...
>>
>>
>> Even though I get this message, apparently. emacsclient does find the
>> network socket and brings up the "~/.emacs" file in an emacs window.
>>
>> In Emacs, invoking `(list-processes)' yields:
>>
>> server listen -- -- (network server on local)
>> server <127.... open -- -- (network connection to 127.0.0.1)
>>
>>
>> .% *Process List* 166 Process Menu
>> * .emacs 73761 Emacs-Lisp ~/.emacs
>> % *GNU Emacs* 858 Fundamental
>> *scratch* 191 Lisp Interaction
>> %* *Messages* 2285 Messages
>>
>>
>> So why give a warning message of "can't find socket" if the connection is
>> subsequentially successful (the server *was* started) and it gets its
>> connection information from the server file, even though the server file
>> is not an actual "socket"?
>>
>> Could it be that invoking emacsclient, by default, first looks for the
>> server socket file in /tmp/emacs<UID>/server ? And then falls back to
>> the ~/.emacs.d/server/server server file if that socket doesn't
>> exists?
>>
>> But because of the default precedence. it doesn't determine whether a
>> server actually doesn't exists before emitting the warning?
>
> (I'm going through old Emacs bug reports that haven't received any
> response.)
>
> I'm unable to reproduce this in Emacs 27. Are you still seeing this
> behaviour?
I'm also unable to reproduce this on Emacs 27. Since more information
was requested, but none was given within 14 weeks, I'm now closing
this bug as unreproducible.
If anyone can reproduce this, please report back and/or reopen the bug
report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2019-11-06 0:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 22:46 bug#23202: 24.5; emacsclient confusing server connection message Live System User
2019-07-28 22:35 ` Lars Ingebrigtsen
2019-11-06 0:45 ` Stefan Kangas [this message]
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=87lfst6de6.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=23202-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=nyc4bos@aol.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).