Vincent Lefevre <vinc...@vinc17.net> writes: > But in any case, the bug needs to be fixed.
Yeah, I don't believe this can reasonably be called a bug. Emacs, like a lot of big complex apps, can and does write to various parts of the filesystem when used. There's a good chance that if you check your home directory, you'll find more files owned by root. Files like .emacs.d/recentf or .emacs.d/auto-save-list/* or .emacs-places. At least, those are some of the files that Emacs has silently modified recently on *my* system. It may depend on which emacs features you have enabled, but that's something you shouldn't have to worry about. Typing "su emacs [filename]" is simply not something you can reasonably expect to do safely. Which is why emacs has features to work around that. Like typing "emacs /su::[filename]" instead. Or using "C-x C-f /su::[filename]" from within emacs. (Or, better yet, "emacs /sudo::[filename]" or "C-x C-f /sudo::[filename]".) If it *really* bothers you to type the pathname, you can make an alias like: "eroot='emacs /sudo::$(pwd)/$1'". Or even "su -l emacs $(pwd)/$1". However, turning off dbus access for emacs, which is something some of us actually *use*, just to support a non-standard and unnecessary workflow, is *not* a good option.
