From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How to view raw text in Emacs?
Date: Fri, 06 Apr 2018 15:59:12 +0300 [thread overview]
Message-ID: <83h8oo1of3.fsf@gnu.org> (raw)
In-Reply-To: <877epkiq6f.fsf@bsb.me.uk> (message from Ben Bacarisse on Fri, 06 Apr 2018 11:29:12 +0100)
> From: Ben Bacarisse <ben.lists@bsb.me.uk>
> Date: Fri, 06 Apr 2018 11:29:12 +0100
>
> >> If Emacs already has a buffer which is visiting the file, you
> >> get the existing buffer, regardless of whether it was created
> >> literally or not.
> >
> > "Same buffer" doesn't mean the same contents. When the file is
> > already being visited, you can get the same buffer, but its contents
> > will be erased and populated anew with literally what's in the file,
> > without any conversions.
>
> That paragraph started with the sentence "You cannot absolutely rely on
> this function to result in visiting the file literally."
It no longer says that, I fixed that misleading text.
> but I think the warning is specifically about using
> find-file-literally in a program
You shouldn't use that function in a program, you should use
insert-file-contents-literally instead.
> when called interactively (at least in 25.1.1) I get a warning that
> emacs can only visit a file in one way at a time and I am prompted
> whether to "revisit" the file (so to speak) or take the existing
> buffer.
Yes, and that's the important part the doc string failed to tell. Now
it does.
prev parent reply other threads:[~2018-04-06 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 18:56 How to view raw text in Emacs? N. Jackson
2018-04-05 19:07 ` Alex Kost
[not found] ` <mailman.11755.1522955247.27995.help-gnu-emacs@gnu.org>
2018-04-05 21:18 ` Ben Bacarisse
2018-04-06 2:57 ` Will Parsons
2018-04-06 7:18 ` Eli Zaretskii
2018-04-06 7:17 ` Eli Zaretskii
[not found] ` <mailman.11771.1522999021.27995.help-gnu-emacs@gnu.org>
2018-04-06 10:29 ` Ben Bacarisse
2018-04-06 12:59 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h8oo1of3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.