From: Paul Eggert <eggert@cs.ucla.edu>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Glenn Morris <rgm@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: emacsclient socket ownership
Date: Wed, 5 Dec 2018 16:49:19 -0800 [thread overview]
Message-ID: <6cee04b9-3c73-badc-6d14-6acb6bac0dd5@cs.ucla.edu> (raw)
In-Reply-To: <87sgzbereu.fsf@web.de>
gksu has been removed from Debian and other GNU/Linux distributions for
maintenance and security reasons (see
<https://jeremy.bicha.net/2018/03/21/gksu-is-dead/>), so I'd rather
focus on any other tools having similar problems. That being said, you
should be able to work around the gksu issue by setting (or unsetting)
XDG_RUNTIME_DIR in gksu's subsidiary environment before invoking Emacs
(not that I recommend using gksu at all...).
prev parent reply other threads:[~2018-12-06 0:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 16:43 emacsclient socket ownership Glenn Morris
2018-11-02 15:38 ` Stefan Monnier
2018-11-02 16:53 ` Yuri Khan
2018-11-02 18:49 ` Stefan Monnier
2018-11-02 20:08 ` Paul Eggert
2018-11-02 20:30 ` Stefan Monnier
2018-11-02 21:06 ` Paul Eggert
2018-11-05 1:13 ` Glenn Morris
2018-11-05 4:46 ` Stefan Monnier
2018-11-05 7:26 ` Paul Eggert
2018-11-06 17:19 ` Daniel Pittman
2018-11-06 17:54 ` Stefan Monnier
2018-11-06 18:17 ` Paul Eggert
2018-11-13 18:21 ` Glenn Morris
2018-11-13 19:25 ` Eli Zaretskii
2018-11-05 5:12 ` Paul Eggert
2018-12-05 18:53 ` Michael Heerdegen
2018-12-05 19:38 ` Glenn Morris
2018-12-05 19:46 ` Eli Zaretskii
2018-12-05 20:02 ` Glenn Morris
2018-12-05 20:19 ` Eli Zaretskii
2018-12-06 0:36 ` Paul Eggert
2018-12-06 6:37 ` Eli Zaretskii
2018-12-06 19:08 ` Paul Eggert
2018-12-06 19:18 ` Eli Zaretskii
2018-12-06 20:26 ` Glenn Morris
2018-12-06 21:01 ` Paul Eggert
2018-12-05 20:33 ` Glenn Morris
2018-12-05 20:58 ` Michael Heerdegen
2018-12-06 0:49 ` Paul Eggert [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6cee04b9-3c73-badc-6d14-6acb6bac0dd5@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.