From: Richard Stallman <rms@gnu.org>
To: Moakt Temporary Email <df0b35e27b55@drmail.in>
Cc: emacs-devel@gnu.org
Subject: Re: A new filter-based customization interface
Date: Thu, 09 Jan 2025 22:24:35 -0500 [thread overview]
Message-ID: <E1tW5dT-0002Qs-P9@fencepost.gnu.org> (raw)
In-Reply-To: <HXzNIHgeLxDBXC3FjDSIFOorb4czrMcLaBam7b9ZEpk@localhost.localdomain> (message from Moakt Temporary Email on Thu, 9 Jan 2025 13:46: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. ]]]
Your idea has both "filters" and "categories". I gather that both
filters and categories select subsets of the set of all the options.
What is the difference between these two kinds of subset?
Which subsets should be "filters" and which should be "categories"?
> 1- This new interface (as you already saw in the image), can put them
> forward.
I understand the general goal here, but _how_, concretely, does this
interface do that?
You talk about general goals, and they make sense as goals.
But in order to be an idea that is possible to consider,
it has to explain _how_ it will make certain options
more discoerable.
--
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:[~2025-01-10 3:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 13:46 A new filter-based customization interface Moakt Temporary Email
2025-01-10 3:24 ` Richard Stallman [this message]
2025-01-10 15:29 ` Björn Bidar
[not found] ` <87o70eptze.fsf@>
2025-01-16 0:06 ` Richard Stallman
2025-01-21 1:20 ` Björn Bidar
[not found] ` <875xm9ufmu.fsf@>
2025-01-21 20:16 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2025-01-14 0:07 Moakt Temporary Email
2025-01-19 20:54 ` Björn Bidar
2025-01-14 0:01 Moakt Temporary Email
2025-01-13 23:44 Moakt Temporary Email
2025-01-13 23:39 Moakt Temporary Email
2025-01-14 12:58 ` Eli Zaretskii
2024-12-31 11:49 Moakt Temporary Email
2025-01-02 4:36 ` Richard Stallman
2025-01-02 4:36 ` Richard Stallman
2025-01-02 4:36 ` Richard Stallman
2025-01-02 4:36 ` Richard Stallman
2025-01-02 4:37 ` Richard Stallman
2024-12-16 22:02 Moakt Temporary Email
2024-12-31 4:43 ` Richard Stallman
2024-12-09 3:37 Moakt Temporary Email
2024-12-10 19:56 ` Philip Kaludercic
2024-12-12 4:48 ` Richard Stallman
2024-12-24 4:51 ` Richard Stallman
2024-12-24 21:10 ` Björn Bidar
[not found] ` <87bjx0oki1.fsf@>
2024-12-26 4:30 ` Richard Stallman
2024-12-29 15:29 ` Björn Bidar
[not found] ` <87o70ucxt5.fsf@>
2024-12-31 4:43 ` Richard Stallman
2025-01-01 20:00 ` Björn Bidar
[not found] ` <87o70quwxo.fsf@>
2025-01-16 0:06 ` Richard Stallman
2024-12-26 4:30 ` Richard Stallman
2024-12-29 20:02 ` Björn Bidar
[not found] ` <87a5ce1clq.fsf@>
2024-12-31 4:43 ` 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
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=E1tW5dT-0002Qs-P9@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=df0b35e27b55@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).