[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#50431: revert-buffer doesn't preserve read-onlyness
From: |
Lars Ingebrigtsen |
Subject: |
bug#50431: revert-buffer doesn't preserve read-onlyness |
Date: |
Sat, 27 Aug 2022 15:15:47 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
> Or not. It could be an accident as well.
Anything is possible, but what's likely?
> "Reverting" has a specific meaning: re-read the file from disk as if
> it were visited anew. If the user wants to make additional
> adjustments, they will need to readjust. I don't see why the
> read-only status should be exempt from this logic.
Just because it's something that people do use, explicitly, to control
the buffer. That's not the case with, say, minor modes, where people
usually switch then on from hooks or globally.
- bug#50431: revert-buffer doesn't preserve read-onlyness, (continued)
- bug#50431: revert-buffer doesn't preserve read-onlyness, Lars Ingebrigtsen, 2022/08/25
- bug#50431: revert-buffer doesn't preserve read-onlyness, Juri Linkov, 2022/08/25
- bug#50431: revert-buffer doesn't preserve read-onlyness, Eli Zaretskii, 2022/08/25
- bug#50431: revert-buffer doesn't preserve read-onlyness, Juri Linkov, 2022/08/25
- bug#50431: revert-buffer doesn't preserve read-onlyness, Eli Zaretskii, 2022/08/26
- bug#50431: revert-buffer doesn't preserve read-onlyness, Juri Linkov, 2022/08/26
- bug#50431: revert-buffer doesn't preserve read-onlyness, Drew Adams, 2022/08/26
- bug#50431: revert-buffer doesn't preserve read-onlyness, Lars Ingebrigtsen, 2022/08/26
- bug#50431: revert-buffer doesn't preserve read-onlyness, Eli Zaretskii, 2022/08/26
- bug#50431: revert-buffer doesn't preserve read-onlyness, Drew Adams, 2022/08/26
- bug#50431: revert-buffer doesn't preserve read-onlyness,
Lars Ingebrigtsen <=