From: Richard Stallman <rms@gnu.org>
To: Moakt Temporary Email <059393ccf4a8@drmail.in>
Cc: emacs-devel@gnu.org
Subject: Re: A new filter-based customization interface
Date: Wed, 01 Jan 2025 23:37:00 -0500 [thread overview]
Message-ID: <E1tTCxA-0002L9-AX@fencepost.gnu.org> (raw)
In-Reply-To: <pFa7llF0JiuSMl1mJUnCZEbwcOM0ktGofrXswuQtBxA@localhost.localdomain> (message from Moakt Temporary Email on Tue, 31 Dec 2024 11:49:23 +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. ]]]
> - beginner-friendly
> Using terms that users may be already familiar with. Users can be
> coming from different backgrounds.
There is an implicit contradiction between those two sentences. To
predict what terms users are familiar with, we need to know their
background. If their backgrounds are diverse, such prediction becomes
harder.
> - gradually introduce users to emacs vocabulary
That is a design goal, not an implementation plan. Realizing that
goal might be ok, or intolerable, depending on the specific way in
which the interface does that.
Emacs has existed for 48 years. Much of its terminology has been the
same since then. By comparison, the other interfaces you are thinking
of are passing fads. There are changes we can make, but rewriting so
much documentation based on a fad would be misguided.
We want to teach users our terminology, not try to speak in theirs.
> While most of the filters would use familiar terms, there are some
> that are emacs-specific. This makes users realize that these words
> are important/special in emacs.
> For example: face, overlay, minibuffer, keybinding, keymap, font-lock,
> narrowing, mark, region, kill ring, mark ring, etc.
That is buried down in the details. I think you have an idea for the
middle level of design, which links the design goal to these details.
You need to describe it clearly.
--
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-02 4:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 11:49 A new filter-based customization interface 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2024-12-26 4:30 ` Richard Stallman
2024-12-27 2:04 ` Madhu
2024-12-27 13:07 ` Jean Louis
2024-12-27 15:16 ` dick.r.chiang
2024-12-28 5:58 ` Joel Reicher
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1tTCxA-0002L9-AX@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=059393ccf4a8@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 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.