From: Richard Stallman <rms@gnu.org>
To: Moakt Temporary Email <emacs-devel-proposal@drmail.in>
Cc: emacs-devel@gnu.org
Subject: Re: A new filter-based customization interface
Date: Mon, 23 Dec 2024 23:51:32 -0500 [thread overview]
Message-ID: <E1tPwtI-0004mV-39@fencepost.gnu.org> (raw)
In-Reply-To: <0NIXA7Y2Px1UnKQELQ6RBx5sxmpLWcCpbzAnquDioY@localhost.localdomain> (message from Moakt Temporary Email on Mon, 9 Dec 2024 03:37:55 +0000)
[[[ 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. ]]]
> I added a screenshot of what such an interface might look like (which
> is better than words). https://justpaste.it/fdau4.
That site seems to depend on nonfree Javascript code. Those of us who
block nonfree Javascript. or block Javascript entirely, cannot see
whatever you meant to show us.
Even worse, there are people on the lis who do not block nonfree
Javascript in their browsers. By referring to that site, you are
promoting the use of nonfree software! And, in the process,
legitimizing the use and distrbution of nonfree software -- which is
the direct opposite of the goal of GNU.
Would you please describe or present your idea in a way that we can
understand without running nonfree software? Then we could all think
about adding it to Emacs.
Emacs already has a general configuration interface, which you can
access using M-x configure. It at least tries to do what you have in
mind. Your approach, if implemented without nonfree software,
might be better in some ways.
Would you like to familiarize yourself with M-x configure and related
commands, see what it does and what it doesn't do, and describe
your idea in terms of how it differs from what we already have?
Do the differences concern manner of display, or the semantics
of the customization methods?
M-x configure displays through Emacs buffers and Emacs redisplay
because that is the facility that is always avaiable (in Emacs).
Using some other basis could look nicer, but would be a lot more work
to implement and to maintain in various situations.
However, different semantics might not have such an obstacle.
--
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:[~2024-12-24 4:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 3:37 A new filter-based customization interface Moakt Temporary Email
2024-12-10 19:56 ` Philip Kaludercic
2024-12-12 4:48 ` Richard Stallman
2024-12-24 4:51 ` Richard Stallman [this message]
2024-12-24 21:10 ` Björn Bidar
[not found] ` <87bjx0oki1.fsf@>
2024-12-26 4:30 ` Richard Stallman
2024-12-26 4:30 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2024-12-16 22:02 Moakt Temporary Email
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1tPwtI-0004mV-39@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel-proposal@drmail.in \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).