bug#23202: 24.5; emacsclient confusing server connection message

[Stefan Kangas]

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