From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: joseph@breatheoutbreathe.in, emacs-devel@gnu.org,
mail+gh@daniel-mendler.de
Subject: Re: [IDEA] Add function clean-buffer
Date: Fri, 08 Sep 2023 20:38:46 -0400 [thread overview]
Message-ID: <E1qelzq-0003m4-IU@fencepost.gnu.org> (raw)
In-Reply-To: <83cyyv342w.fsf@gnu.org> (message from Eli Zaretskii on Wed, 06 Sep 2023 14:59:19 +0300)
[[[ 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. ]]]
Why make this command kill local variables?
Most buffer-local variables come from the major mode.
Is it really desirable to reliminate the major mode?
Eliminating the major mode is what `fundamental-mode' does.
Text properties are usually related to the major mode,
often due to Font Lock mode.
Should `fundamental-mode' eliminate text properties? Or perhaps only
some text properties?
Should `clean-buffer' eliminate only the text properties and overlays
that do NOT come from the major mode?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2023-09-09 0:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 22:18 [IDEA] Add function clean-buffer Joseph Turner
2023-09-04 16:02 ` Philip Kaludercic
2023-09-05 19:37 ` Joseph Turner
2023-09-06 11:59 ` Eli Zaretskii
2023-09-08 4:55 ` Joseph Turner
2023-09-08 9:13 ` David Ponce
2023-09-08 17:21 ` Joseph Turner
2023-09-09 0:38 ` Richard Stallman [this message]
2023-09-09 0:59 ` Joseph Turner
2023-09-09 7:00 ` Eli Zaretskii
2023-09-10 8:19 ` Stefan Kangas
2023-09-12 0:29 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1qelzq-0003m4-IU@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joseph@breatheoutbreathe.in \
--cc=mail+gh@daniel-mendler.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.