summaryrefslogtreecommitdiff
path: root/devdocs/elisp/loading-non_002dascii.html
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2025-08-14 22:58:58 -0500
committerCraig Jennings <c@cjennings.net>2025-08-14 22:58:58 -0500
commit82ba818ff456bcd6d56a06226e3f27e98fbb55c3 (patch)
tree158cfc17b2f644a10f063cb546752cfaae12c97f /devdocs/elisp/loading-non_002dascii.html
parent9278ddd4ea1a8b1a4c1edaa8894516e3f48d245b (diff)
downloaddotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.tar.gz
dotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.zip
removing all downloaded devdocs files
Diffstat (limited to 'devdocs/elisp/loading-non_002dascii.html')
-rw-r--r--devdocs/elisp/loading-non_002dascii.html6
1 files changed, 0 insertions, 6 deletions
diff --git a/devdocs/elisp/loading-non_002dascii.html b/devdocs/elisp/loading-non_002dascii.html
deleted file mode 100644
index 094e2ec4..00000000
--- a/devdocs/elisp/loading-non_002dascii.html
+++ /dev/null
@@ -1,6 +0,0 @@
- <h3 class="section">Loading Non-ASCII Characters</h3> <p>When Emacs Lisp programs contain string constants with non-<acronym>ASCII</acronym> characters, these can be represented within Emacs either as unibyte strings or as multibyte strings (see <a href="text-representations">Text Representations</a>). Which representation is used depends on how the file is read into Emacs. If it is read with decoding into multibyte representation, the text of the Lisp program will be multibyte text, and its string constants will be multibyte strings. If a file containing Latin-1 characters (for example) is read without decoding, the text of the program will be unibyte text, and its string constants will be unibyte strings. See <a href="coding-systems">Coding Systems</a>. </p> <p>In most Emacs Lisp programs, the fact that non-<acronym>ASCII</acronym> strings are multibyte strings should not be noticeable, since inserting them in unibyte buffers converts them to unibyte automatically. However, if this does make a difference, you can force a particular Lisp file to be interpreted as unibyte by writing ‘<samp>coding: raw-text</samp>’ in a local variables section. With that designator, the file will unconditionally be interpreted as unibyte. This can matter when making keybindings to non-<acronym>ASCII</acronym> characters written as <code>?v<var>literal</var></code>. </p><div class="_attribution">
- <p class="_attribution-p">
- Copyright &copy; 1990-1996, 1998-2022 Free Software Foundation, Inc. <br>Licensed under the GNU GPL license.<br>
- <a href="https://www.gnu.org/software/emacs/manual/html_node/elisp/Loading-Non_002dASCII.html" class="_attribution-link">https://www.gnu.org/software/emacs/manual/html_node/elisp/Loading-Non_002dASCII.html</a>
- </p>
-</div>