unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>, Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacsclient socket ownership
Date: Sun, 4 Nov 2018 23:26:28 -0800	[thread overview]
Message-ID: <a36bdfdb-64d5-89a2-e401-08822a95b9eb@cs.ucla.edu> (raw)
In-Reply-To: <jwvva5c16g2.fsf-monnier+emacs@gnu.org>

Stefan Monnier wrote:
> /run is not an option for non-root users, I believe.

It works for me on Ubuntu 18.04.1 and seems to be used for this sort of thing:

$ ls -ld $XDG_RUNTIME_DIR
drwx------ 11 eggert eggert 260 Nov  4 23:21 /run/user/1000
$ mkdir $XDG_RUNTIME_DIR/emacs
$ ls -l $XDG_RUNTIME_DIR
total 0
srw-rw-rw-  1 eggert eggert   0 Nov  4 08:32 bus
drwx------  3 eggert eggert  60 Nov  4 08:32 dbus-1
drwx------  2 eggert eggert  60 Nov  4 23:18 dconf
drwxr-xr-x  2 eggert eggert  40 Nov  4 23:21 emacs
drwx--x--x  2 eggert eggert  60 Nov  4 08:32 gdm
drwx------  3 eggert eggert  60 Nov  4 08:32 gnome-shell
drwx------  2 eggert eggert 140 Nov  4 08:32 gnupg
dr-x------  2 eggert eggert   0 Nov  4 08:32 gvfs
drwx------  2 eggert eggert 120 Nov  4 08:43 keyring
drwx------  2 eggert eggert  80 Nov  4 08:32 pulse
drwxr-xr-x  2 eggert eggert  80 Nov  4 08:32 systemd
-rw-------  1 eggert eggert   0 Nov  4 08:33 update-notifier.pid



  reply	other threads:[~2018-11-05  7:26 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 [this message]
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

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=a36bdfdb-64d5-89a2-e401-08822a95b9eb@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --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 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).