From: Noam Postavsky <npostavs@gmail.com>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: 32413@debbugs.gnu.org
Subject: bug#32413: 25.2; When run as root, emacs writes dconf files in a non-root user's /run/user/XXX directory
Date: Sun, 12 Aug 2018 13:31:08 -0400 [thread overview]
Message-ID: <87d0unwkyr.fsf@gmail.com> (raw)
In-Reply-To: <20180810155310.GF12819@zira.vinc17.org> (Vincent Lefevre's message of "Fri, 10 Aug 2018 17:53:10 +0200")
tags 32413 notabug
close 32413
quit
>> The specific example of dconf etc is not a bug, it's how these things
>> work. If you don't like it, use the configure option to disable that
>> feature (most programs won't give you that option). I think the general
>> principle of "Emacs should never create files/directories if the user
>> hasn't explicitly asked it to do that" is a non-starter.
>> So this report should be closed wontfix IMO.
>
> I'm using Debian's package. So, you are saying that Debian should
> use this option?
You should either stop using Debian's package (since you don't like the
options they choose), or see if you can convince them to use that
option.
I think it's clear enough that ./configure --without-gsettings is as
much of a fix as there's ever going to be, so I'm closing this bug.
next prev parent reply other threads:[~2018-08-12 17:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 9:30 bug#32413: 25.2; When run as root, emacs writes dconf files in a non-root user's /run/user/XXX directory Vincent Lefevre
2018-08-10 12:17 ` Eli Zaretskii
2018-08-10 12:57 ` Vincent Lefevre
2018-08-10 13:47 ` Eli Zaretskii
2018-08-10 14:32 ` Vincent Lefevre
2018-08-10 15:41 ` Glenn Morris
2018-08-10 15:53 ` Vincent Lefevre
2018-08-12 17:31 ` Noam Postavsky [this message]
2018-08-12 22:03 ` Andreas Schwab
2018-08-12 23:45 ` Glenn Morris
2018-08-10 19:39 ` Eli Zaretskii
2018-08-10 12:28 ` Noam Postavsky
2018-08-10 12:39 ` Eli Zaretskii
2018-08-12 17:28 ` Noam Postavsky
2018-08-10 14:17 ` Vincent Lefevre
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=87d0unwkyr.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=32413@debbugs.gnu.org \
--cc=vincent@vinc17.net \
/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).