From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20675@debbugs.gnu.org, Bruce Korb <bruce.korb@gmail.com>
Subject: bug#20675: 24.3; emacsclient cannot talk to emacs
Date: Tue, 1 Oct 2019 20:54:31 +0200 [thread overview]
Message-ID: <CADwFkm=KEib0hCHM_ov+7hubQ4BB++AfW-jsafaHfa0F_9H7Ww@mail.gmail.com> (raw)
In-Reply-To: <831rvw9uo5.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> > I see that server-socket-dir is documented in the Emacs FAQ, but not
> > at all in the manual.
>
> That's because the right way of controlling this is by customizing
> server-name, not server-socket-dir. See the user manual about
> server-name.
Right, but then it still seems like the documentation has a problem.
For starters, server-socket-dir is extensively documented in the FAQ,
while server-name is not at all mentioned. Does that really make
sense if we want users to use server-name?
From the FAQ:
> Emacs by default creates a Unix domain socket
> named ‘server’ in a well-known directory, typically
> ‘$XDG_RUNTIME_DIR/emacs’ if Emacs is running under an X Window
> System desktop and ‘$TMPDIR/emacsUSERID’ otherwise. See the
> variable ‘server-socket-dir’. Traditionally, Emacs used
> ‘$TMPDIR/emacsUSERID’ even when running under an X desktop; if you
> prefer this traditional (and less-secure) behavior, you can set the
> environment variable ‘EMACS_SOCKET_NAME’ to
> ‘$TMPDIR/emacsUSERID/server’ before invoking Emacs and
> ‘emacsclient’, although it will be your responsibility to create
> the directory ‘$TMPDIR/emacsUSERID’ with appropriate ownership and
> permissions.
Perhaps this entire text should be moved to the doc string of the
sparsely documented server-socket-dir, with a note that the user
should use server-name instead? And the FAQ updated to direct users
to use server-name?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-10-01 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 18:09 bug#20675: 24.3; emacsclient cannot talk to emacs Bruce Korb
2019-09-29 23:46 ` Stefan Kangas
2019-10-01 17:31 ` Bruce Korb
2019-10-01 18:05 ` Stefan Kangas
2019-10-01 18:39 ` Eli Zaretskii
2019-10-01 18:54 ` Stefan Kangas [this message]
2019-10-01 19:13 ` Eli Zaretskii
2019-10-02 13:37 ` Stefan Kangas
2019-10-02 15:29 ` Eli Zaretskii
2019-10-02 15:33 ` Stefan Kangas
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='CADwFkm=KEib0hCHM_ov+7hubQ4BB++AfW-jsafaHfa0F_9H7Ww@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=20675@debbugs.gnu.org \
--cc=bruce.korb@gmail.com \
--cc=eliz@gnu.org \
/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).