summaryrefslogtreecommitdiff
path: root/devdocs/elisp/visiting-files.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/visiting-files.html
parent9278ddd4ea1a8b1a4c1edaa8894516e3f48d245b (diff)
downloaddotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.tar.gz
dotemacs-82ba818ff456bcd6d56a06226e3f27e98fbb55c3.zip
removing all downloaded devdocs files
Diffstat (limited to 'devdocs/elisp/visiting-files.html')
-rw-r--r--devdocs/elisp/visiting-files.html16
1 files changed, 0 insertions, 16 deletions
diff --git a/devdocs/elisp/visiting-files.html b/devdocs/elisp/visiting-files.html
deleted file mode 100644
index 59415c5d..00000000
--- a/devdocs/elisp/visiting-files.html
+++ /dev/null
@@ -1,16 +0,0 @@
- <h3 class="section">Visiting Files</h3> <p>Visiting a file means reading a file into a buffer. Once this is done, we say that the buffer is <em>visiting</em> that file, and call the file <em>the visited file</em> of the buffer. </p> <p>A file and a buffer are two different things. A file is information recorded permanently in the computer (unless you delete it). A buffer, on the other hand, is information inside of Emacs that will vanish at the end of the editing session (or when you kill the buffer). When a buffer is visiting a file, it contains information copied from the file. The copy in the buffer is what you modify with editing commands. Changes to the buffer do not change the file; to make the changes permanent, you must <em>save</em> the buffer, which means copying the altered buffer contents back into the file. </p> <p>Despite the distinction between files and buffers, people often refer to a file when they mean a buffer and vice-versa. Indeed, we say, “I am editing a file”, rather than, “I am editing a buffer that I will soon save as a file of the same name”. Humans do not usually need to make the distinction explicit. When dealing with a computer program, however, it is good to keep the distinction in mind. </p> <table class="menu" border="0" cellspacing="0"> <tr>
-<td align="left" valign="top">• <a href="visiting-functions" accesskey="1">Visiting Functions</a>
-</td>
-<td> </td>
-<td align="left" valign="top">The usual interface functions for visiting. </td>
-</tr> <tr>
-<td align="left" valign="top">• <a href="subroutines-of-visiting" accesskey="2">Subroutines of Visiting</a>
-</td>
-<td> </td>
-<td align="left" valign="top">Lower-level subroutines that they use. </td>
-</tr> </table><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/Visiting-Files.html" class="_attribution-link">https://www.gnu.org/software/emacs/manual/html_node/elisp/Visiting-Files.html</a>
- </p>
-</div>