bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#13298: 24.3.50; Cannot write backup file; backing up in ~\.emacs.d\%


From: Eli Zaretskii
Subject: bug#13298: 24.3.50; Cannot write backup file; backing up in ~\.emacs.d\%backup%~
Date: Sat, 29 Dec 2012 19:28:31 +0200

> Date: Sat, 29 Dec 2012 21:18:54 +0400
> From: Dmitry Gutov <dgutov@yandex.ru>
> CC: 13298@debbugs.gnu.org
> 
> Why doesn't Emacs try to show the elevation dialog, anyway?

The elevation dialog comes from Windows, when it does.  Applications
don't show it, they just can trigger it by performing operations that
require elevation.  But UAC behaves strangely when Administrators are
involved.

> >> Like I described, I don't think my situation is exceptional, so seeing
> >> the error messages is misleading.
> >
> > Why misleading?  We asked Emacs to preserve the ACLs of the original
> > file, and it couldn't.  Shouldn't the user be informed about that?
> 
> It leads me to believe that there's either something wrong with my 
> system, or Emacs configuration, whereas I don't know why I should care 
> that the backup function doesn't correctly set the file ownership.

You could try taking care of this issue by manually taking ownership
of the C:\Users\Gutov directory and all of its files and
subdirectories.  Setting the owner of C:\Users\Gutov to either your
user or the Administrators group will probably resolve the problem.
Doing the former, i.e. setting your user as the owner, sounds like TRT
to me anyway, it doesn't make sense to me to have SYSTEM as an owner.

> > If you think this is bad behavior, lobby on emacs-devel to allow some
> > kind of user options for ignoring these errors (which means you don't
> > care about security of access to your files).
> 
> I don't think that a user option is the way to go if it's going to be 
> off by default.
> 
> Maybe don't expect the user to customize its value, and bind it to t in 
> certain functions, like backup-buffer-copy, instead?

I will let others answer that.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]