* lisp/files.el (find-file-literally): Doc fix.
This commit is contained in:
parent
9b24a7937a
commit
5659b2fe84
1 changed files with 9 additions and 4 deletions
|
@ -2342,10 +2342,15 @@ and local variable specifications in the file are ignored.
|
||||||
Automatic uncompression and adding a newline at the end of the
|
Automatic uncompression and adding a newline at the end of the
|
||||||
file due to `require-final-newline' is also disabled.
|
file due to `require-final-newline' is also disabled.
|
||||||
|
|
||||||
You cannot absolutely rely on this function to result in
|
If Emacs already has a buffer which is visiting the file,
|
||||||
visiting the file literally. If Emacs already has a buffer
|
this command asks you whether to visit it literally instead.
|
||||||
which is visiting the file, you get the existing buffer,
|
|
||||||
regardless of whether it was created literally or not.
|
In non-interactive use, the value is the buffer where the file is
|
||||||
|
visited literally. If the file was visited in a buffer before
|
||||||
|
this command was invoked, it will reuse the existing buffer,
|
||||||
|
regardless of whether it was created literally or not; however,
|
||||||
|
the contents of that buffer will be the literal text of the file
|
||||||
|
without any conversions.
|
||||||
|
|
||||||
In a Lisp program, if you want to be sure of accessing a file's
|
In a Lisp program, if you want to be sure of accessing a file's
|
||||||
contents literally, you should create a temporary buffer and then read
|
contents literally, you should create a temporary buffer and then read
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue