emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#65005: closed (server hangs forever if not properly initialized)


From: GNU bug Tracking System
Subject: bug#65005: closed (server hangs forever if not properly initialized)
Date: Mon, 23 Oct 2023 20:09:02 +0000

Your message dated Mon, 23 Oct 2023 13:07:48 -0700
with message-id 
<CADwFkmnTnL7Hvdn7rCyEw=iZNs_tCBnWMGjsgAiv4jj_vUJuJQ@mail.gmail.com>
and subject line Re: bug#65005: server hangs forever if not properly initialized
has caused the debbugs.gnu.org bug report #65005,
regarding server hangs forever if not properly initialized
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
65005: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65005
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: server hangs forever if not properly initialized Date: Tue, 1 Aug 2023 18:24:35 -0500
server-start fails to start, with the message:

apply: Cannot bind server socket: No such file or directory

To reproduce:

1. Kill any existing emacs-server
2. Rename or delete $XDG_RUNTIME_DIR/emacs
3. Execute server-start


The problem is that the directory specified in XDG_RUNTIME_DIR existed, but with no emacs subdirectory. I do believe that emacs ought simply create the directory



--- End Message ---
--- Begin Message --- Subject: Re: bug#65005: server hangs forever if not properly initialized Date: Mon, 23 Oct 2023 13:07:48 -0700
Eli Zaretskii <eliz@gnu.org> writes:

>> The problem is that the directory specified in XDG_RUNTIME_DIR existed, but 
>> with no emacs
>> subdirectory. I do believe that emacs ought simply create the directory
>
> It already does, so I cannot reproduce the problem you see.
>
> In which version of Emacs did you see this?  Your report doesn't
> include the details of your build.

More information was requested, but none was given within 12 weeks, so
I'm closing this bug.  If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]