diff options
| author | Lars Ingebrigtsen <larsi@gnus.org> | 2021-09-13 15:17:02 +0200 |
|---|---|---|
| committer | Lars Ingebrigtsen <larsi@gnus.org> | 2021-09-13 15:17:06 +0200 |
| commit | 59ff342869062caba72af7834c00b36753fa7461 (patch) | |
| tree | 3f0dbc597da34f8d6c83c75185f2f721ad20fe99 /lisp/files.el | |
| parent | e4a187ca5908f5e151fd42b9ab7b72bc5a9bfc2a (diff) | |
Mention unibyte issues in insert-file-contents-literally doc string
* lisp/files.el (insert-file-contents-literally): Mention possible
issues with multibyte buffers (bug#50560).
Diffstat (limited to 'lisp/files.el')
| -rw-r--r-- | lisp/files.el | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/lisp/files.el b/lisp/files.el index 67c4628468b..821be1eb2c6 100644 --- a/lisp/files.el +++ b/lisp/files.el @@ -2526,7 +2526,14 @@ A buffer may be modified in several ways after reading into the buffer, due to Emacs features such as format decoding, character code conversion, `find-file-hook', automatic uncompression, etc. -This function ensures that none of these modifications will take place." +This function ensures that none of these modifications will take place. + +Unlike `find-file-literally', this function does not make the +buffer unibyte, so if this function is used when handling +binary (non-character) data, it can be convenient to make the +buffer unibyte first. This isn't, strictly speaking, necessary, +because multibyte buffers can also deal with raw bytes. See info +node `(elisp)Character Codes' for details.") (let ((format-alist nil) (after-insert-file-functions nil) (coding-system-for-read 'no-conversion) |