From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: 18141@debbugs.gnu.org, yamaoka@jpl.org
Subject: bug#18141: 24.4.50; saving .gz file breaks file coding
Date: Thu, 07 Aug 2014 08:20:06 -0400 [thread overview]
Message-ID: <jwv38d8a437.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <20140807003116.GM4813@xvii.vinc17.org> (Vincent Lefevre's message of "Thu, 7 Aug 2014 02:31:16 +0200")
> Ctrl-C is safe with any correctly written software.
Agreed.
> It's more than 5 times as fast, thus very relevant.
Agreed (I also use C-c on a regular basis to exit Emacs).
> 1 GB costs 0.10 EUR per month, and I don't want to waste several
> dozens of GB of backups (easily produced without clean-up). Once
> becoming useless, backup files have no value.
Note that in this specific case, the problem only happens if you ask
Emacs to keep backups. I have set make-backup-files to nil many years
ago and never looked back (all the files where it might matter are under
some kind of VCS anyway).
>> After r111638, the prompt is issued before backing up the file.
> And that's a much more logical sequence.
Indeed. The problem is that this is done by changing the moment at
which the coding-system is chosen (and makes it "too early") instead of
changing the moment at which the backup is made (which is the right
thing to do, but requires more significant changes in the code).
Stefan
next prev parent reply other threads:[~2014-08-07 12:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 6:59 bug#18141: 24.4.50; saving .gz file breaks file coding Katsumi Yamaoka
2014-07-30 0:10 ` Glenn Morris
2014-07-30 2:36 ` Katsumi Yamaoka
2014-07-30 13:15 ` Katsumi Yamaoka
2014-08-05 8:34 ` Glenn Morris
2014-08-06 14:36 ` Eli Zaretskii
2014-08-06 16:43 ` Vincent Lefevre
2014-08-06 17:32 ` Eli Zaretskii
2014-08-06 19:08 ` Vincent Lefevre
2014-08-06 19:45 ` Eli Zaretskii
2014-08-07 0:31 ` Vincent Lefevre
2014-08-07 12:20 ` Stefan Monnier [this message]
2014-08-07 14:23 ` Vincent Lefevre
2014-08-11 1:06 ` Glenn Morris
2014-08-06 17:48 ` Stefan Monnier
2014-08-06 18:10 ` Eli Zaretskii
2014-08-07 0:45 ` Stefan Monnier
2014-08-07 15:14 ` Eli Zaretskii
2014-08-07 19:08 ` Stefan Monnier
2014-08-07 19:37 ` Eli Zaretskii
2014-08-07 20:43 ` Stefan Monnier
2014-08-08 5:51 ` Eli Zaretskii
2014-08-06 23:45 ` Glenn Morris
2014-08-07 0:03 ` Glenn Morris
2014-08-07 12:14 ` Stefan Monnier
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=jwv38d8a437.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18141@debbugs.gnu.org \
--cc=vincent@vinc17.net \
--cc=yamaoka@jpl.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).