[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#18141: 24.4.50; saving .gz file breaks file coding
From: |
Stefan Monnier |
Subject: |
bug#18141: 24.4.50; saving .gz file breaks file coding |
Date: |
Thu, 07 Aug 2014 16:43:05 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) |
> We could add a new optional argument to write-region to control
> whether backup is performed.
We could. But I think write-region is already too big with too
many arguments. I'd rather try to split it up into sub-components,
which is desirable in and of itself.
But that's just my preference, and I won't oppose a patch that takes
a different route.
> I think users generally expect this to be a transaction. And at least
> on Posix platforms, where rename is an atomic operation, we can
> achieve this, or come pretty close.
I think the time-window is inevitable as long as we do "move first, then
write the new file". Of course, we could do it the "precious"
way instead (i.e. write the new file first and then do the needed
link&unlink to move it into place).
Stefan
- bug#18141: 24.4.50; saving .gz file breaks file coding, (continued)
bug#18141: 24.4.50; saving .gz file breaks file coding, Stefan Monnier, 2014/08/06
- bug#18141: 24.4.50; saving .gz file breaks file coding, Eli Zaretskii, 2014/08/06
- bug#18141: 24.4.50; saving .gz file breaks file coding, Stefan Monnier, 2014/08/06
- bug#18141: 24.4.50; saving .gz file breaks file coding, Eli Zaretskii, 2014/08/07
- bug#18141: 24.4.50; saving .gz file breaks file coding, Stefan Monnier, 2014/08/07
- bug#18141: 24.4.50; saving .gz file breaks file coding, Eli Zaretskii, 2014/08/07
- bug#18141: 24.4.50; saving .gz file breaks file coding,
Stefan Monnier <=
- bug#18141: 24.4.50; saving .gz file breaks file coding, Eli Zaretskii, 2014/08/08
bug#18141: 24.4.50; saving .gz file breaks file coding, Glenn Morris, 2014/08/06
bug#18141: 24.4.50; saving .gz file breaks file coding, Glenn Morris, 2014/08/06