From: Ulrich Mueller <ulm@gentoo.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jporterbugs@gmail.com, ulm@gentoo.org,
Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,
emacs-devel@gnu.org
Subject: Re: emacsclient startup messages
Date: Fri, 05 Nov 2021 10:40:48 +0100 [thread overview]
Message-ID: <uh7crx7mn@gentoo.org> (raw)
In-Reply-To: <83bl2zdo4u.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 05 Nov 2021 10:04:33 +0200")
>>>>> On Fri, 05 Nov 2021, Eli Zaretskii wrote:
>> I have been applying the patch to my Ubuntu 20.04 builds for a couple
>> of days and everything as worked well. Wouldn't it be a good time to
>> put it into emacs-28?
> Not yet.
> Ulrich, any comments on this? Including its importance for Emacs 28?
I've just tested with current master.
The patch breaks the workflow used with Gentoo's app-emacs/emacs-daemon
package. That is, a persistent Emacs daemon started with its socket in
${TMPDIR}/emacs${UID}/server, and emacsclient started with XDG_*
variables in its environment:
$ emacsclient -t --alternate-editor=
emacsclient: can't find socket; have you started the server?
emacsclient: To start the server in Emacs, type "M-x server-start".
Another Emacs daemon is already running at process id 6084
Error: server did not start correctly
Error: Could not start the Emacs daemon
$
I haven't looked into the details of the code yet, but shouldn't the
client first try to connect to an existing socket at both possible
locations? And only start a new daemon when both attempts have failed?
next prev parent reply other threads:[~2021-11-05 9:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 5:26 emacsclient startup messages Pedro Andres Aranda Gutierrez
2021-10-26 12:18 ` Eli Zaretskii
2021-10-26 16:43 ` Pedro Andres Aranda Gutierrez
2021-10-26 16:32 ` Jim Porter
2021-10-26 16:46 ` Pedro Andres Aranda Gutierrez
2021-10-26 17:03 ` Jim Porter
2021-10-27 5:05 ` Pedro Andres Aranda Gutierrez
2021-10-30 17:39 ` Ulrich Mueller
2021-10-30 19:16 ` Jim Porter
2021-10-30 19:47 ` Jim Porter
2021-10-31 10:03 ` Pedro Andres Aranda Gutierrez
2021-10-31 15:44 ` Pedro Andres Aranda Gutierrez
2021-11-05 7:04 ` Pedro Andres Aranda Gutierrez
2021-11-05 8:04 ` Eli Zaretskii
2021-11-05 9:40 ` Ulrich Mueller [this message]
2021-11-05 16:35 ` Jim Porter
2021-11-05 17:52 ` Ulrich Mueller
2021-11-06 11:35 ` Pedro Andres Aranda Gutierrez
2021-11-06 18:40 ` Jim Porter
2021-11-07 9:49 ` Peter Oliver
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=uh7crx7mn@gentoo.org \
--to=ulm@gentoo.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=paaguti@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).