GNU bug report logs -
#18693
25.0.50; backup user options
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Sun, 12 Oct 2014 01:30:05 UTC
Severity: wishlist
Tags: wontfix
Found in version 25.0.50
Done: Stefan Kangas <stefan <at> marxist.se>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18693 in the body.
You can then email your comments to 18693 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18693
; Package
emacs
.
(Sun, 12 Oct 2014 01:30:05 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Drew Adams <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 12 Oct 2014 01:30:06 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
There are several user options for customizing file backups
(`backup-by-*'). Wading through the doc strings or Customize buffers
for them, it seems that they could all be consolidated under option
`make-backup-files', by letting different non-nil values provide the
different backup behaviors.
To be clear: I really don't care about this. Consider it feedback that
it seems that Emacs is making things unnecessarily complicated for
users, here, and it should be possible to do things better. If no one
wants to do that, fine.
Also, things have been like this since at least Emacs 20, and users
already have various `backup-by-*' options in their custom or init
files. So if this were simplified then some remapping/aliasing would
need to happen.
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2014-10-06 on LEG570
Bzr revision: 118063 monnier <at> iro.umontreal.ca-20141006174756-y7ha091r491l1ijw
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
CPPFLAGS=-DGLYPH_DEBUG=1'
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18693
; Package
emacs
.
(Fri, 22 Oct 2021 23:44:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 18693 <at> debbugs.gnu.org (full text, mbox):
tags 18693 + wontfix
close 18693
thanks
Drew Adams <drew.adams <at> oracle.com> writes:
> There are several user options for customizing file backups
> (`backup-by-*'). Wading through the doc strings or Customize buffers
> for them, it seems that they could all be consolidated under option
> `make-backup-files', by letting different non-nil values provide the
> different backup behaviors.
>
> To be clear: I really don't care about this. Consider it feedback that
> it seems that Emacs is making things unnecessarily complicated for
> users, here, and it should be possible to do things better. If no one
> wants to do that, fine.
Thanks for this feature request.
As far as I can tell we have the following options:
backup-by-copying
User option: Non-nil means always use copying to create backup
files.
backup-by-copying-when-linked
User option: Non-nil means use copying to create backups for files
with multiple names.
backup-by-copying-when-mismatch
User option: Non-nil means create backups by copying if this
preserves owner or group.
backup-by-copying-when-privileged-mismatch
User option: Non-nil means create backups by copying to preserve a
privileged owner.
backup-directory-alist
User option: Alist of file name patterns and backup directory names.
backup-enable-predicate
Variable: Predicate that looks at a file name and decides whether to
make backups.
backup-inhibited
Variable: If non-nil, backups will be inhibited.
All in all, I don't think it is too bad. The options clearly express
what they do, and they seem orthogonal to each other.
> Also, things have been like this since at least Emacs 20, and users
> already have various `backup-by-*' options in their custom or init
> files. So if this were simplified then some remapping/aliasing would
> need to happen.
More importantly, and as you correctly observe, creating a consolidated
variable, even if it is a good idea (maybe it is), would lead to a lot
of user configurations breaking or needing updating. So on balance, I
don't think this is worth spending time on or doing, and I'm therefore
closing this bug report.
Added tag(s) wontfix.
Request was from
Stefan Kangas <stefan <at> marxist.se>
to
control <at> debbugs.gnu.org
.
(Fri, 22 Oct 2021 23:44:02 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
18693 <at> debbugs.gnu.org and Drew Adams <drew.adams <at> oracle.com>
Request was from
Stefan Kangas <stefan <at> marxist.se>
to
control <at> debbugs.gnu.org
.
(Fri, 22 Oct 2021 23:44:03 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 20 Nov 2021 12:24:09 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 158 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.