bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#30685: end-of-file mode should respect read-only mode


From: Richard Stallman
Subject: bug#30685: end-of-file mode should respect read-only mode
Date: Wed, 07 Mar 2018 17:58:02 -0500

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

In general, modes and settings of a buffer are not part of
its contents.  The contents of a buffer are the characters
and their text properties.

I see the manual doesn't state this basic point anywhere,
so would someone please install this patch?

I think it belongs in the Emacs 26 manual as well as the current
manual.


diff -u /home/rms/emacs-git/build-nov-15/doc/emacs/buffers.texi.\~1\~ 
/home/rms/emacs-git/build-nov-15/doc/emacs/buffers.texi
--- /home/rms/emacs-git/build-nov-15/doc/emacs/buffers.texi.~1~ 2017-11-09 
12:20:47.729828394 -0500
+++ /home/rms/emacs-git/build-nov-15/doc/emacs/buffers.texi     2018-03-07 
04:43:40.211708142 -0500
@@ -32,6 +32,12 @@
 that window is current.  When there are multiple windows, the buffer
 displayed in the @dfn{selected window} is current.  @xref{Windows}.
 
+@cindex buffer contents
+@cindex contents of a buffer
+  A buffer's @dfn{contents} consist of a series of characters, each of
+which optionally carries a set of text properties (@pxref{Enriched Text})
+which can specify more information about that character.
+
   Aside from its textual contents, each buffer records several pieces
 of information, such as what file it is visiting (if any), whether it
 is modified, and what major mode and minor modes are in effect

Diff finished.  Wed Mar  7 04:43:48 2018

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]