From: Colin Baxter <m43cap@yandex.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: , emacs-devel@gnu.org
Subject: Re: reverting non-existent file
Date: Thu, 14 May 2020 19:52:29 +0100 [thread overview]
Message-ID: <87h7wiic2a.fsf@yandex.com> (raw)
In-Reply-To: <83o8qq4bsm.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 14 May 2020 21:22:01 +0300")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>> From: Colin Baxter <m43cap@yandex.com> Date: Thu, 14 May 2020
>> 17:13:22 +0100
>>
>> 1. emacs -Q <RET> 2. C-x C-f some-non-existing-file-name <RET>
>> 3. M-x add-file-local-variable-prop-line <RET> 4. coding <RET>
>> 5. iso-2022-jp <RET> 6. Told to revert file for effect to take
>> place. 7. M-x revert-buffer <RET> 8. yes <RET> 9. Told cannot
>> revert nonexistent file.
>>
>> The same effect occurs with other codings, for example utf-16 -
>> but not with utf-8-unix. I'm using emacs-28.0.50.
> I get the error message even if I don't do steps 3 to 6. And that
> is expected, as a non-existent file cannot be reverted. So what
> did you find surprising in this behavior?
> (I'm guessing that your locale uses UTF-8 as its codeset, so the
> new file's buffer has utf-8 encoding from the get-go, and thus
> adding the local variable doesn't change the coding-system, and
> you are not asked to revert the buffer. Which is also expected.)
> Confused.
Not now, thanks. I think I was confused by the response "revert-buffer"
when I knew I'd yet to save it. And yes, my locale is utf-8. Sorry to waste
your time.
Best wishes,
--
Colin Baxter
URL: http://www.Colin-Baxter.com
next prev parent reply other threads:[~2020-05-14 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 16:13 reverting non-existent file Colin Baxter
2020-05-14 18:22 ` Eli Zaretskii
2020-05-14 18:52 ` Colin Baxter [this message]
2020-05-14 19:02 ` Eli Zaretskii
2020-05-14 19:54 ` Richard Copley
2020-05-15 5:36 ` Colin Baxter
2020-05-15 7:15 ` Eli Zaretskii
2020-05-15 6:16 ` Eli Zaretskii
2020-05-14 19:58 ` 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=87h7wiic2a.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).