From: Moakt Temporary Email <6bbf4f1ea5cc@drmail.in>
To: emacs-devel@gnu.org
Subject: Re: A new filter-based customization interface
Date: Tue, 14 Jan 2025 00:07:10 +0000 [thread overview]
Message-ID: <s8djpJmsV7O7Rr2IBfgRIQsbtEd3TtUEYxCyXsjcg@localhost.localdomain> (raw)
Hi Björn,
Thank you for your interest in the topic.
> I don't want change any term either but Moakt's explanation is very
> valid. Just shrugging and call of an argument is not good I think.
>
> Language, terminologies evolve and change over time so do interfaces.
> I think it's inevitable that even Emacs has to go with the time
> in some shape or form. Requiring or expecting users to learn 48 old
> language with outdated legacy term is very off putting.
You might be right. But changing the terminology of a software that existed for such a long time, can be a tedious task. There are also many documentations, blogs, books, videos, etc, that would get obsolete.
The question that can come up, is it worth to be done ? Or in other words, what this would “really” bring “vs” the things that it would break ?
Wouldn’t it be better to put all these efforts in other places, which can make emacs easier to start with, like the new customization interface for example, which might be a bigger obstacle, and might have a bigger impact on new users ?
These terms might not finally be the real obstacle for new users to chose emacs, if they are well presented and explained. I thought about it for a while, and proposed a “Get started” introduction to emacs (to be accessed from the very startup buffer).
It will introduce users to some of these terms that are really needed to start using emacs. And the new interface can take care of the remaining terms.
I would be glad if you can take some time and read it, and let me know what do you think. It is the HTML at the end of the following message: https://lists.gnu.org/archive/html/emacs-devel/2024-10/msg00245.html.
Thank you again
next reply other threads:[~2025-01-14 0:07 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 0:07 Moakt Temporary Email [this message]
2025-01-19 20:54 ` A new filter-based customization interface Björn Bidar
-- strict thread matches above, loose matches on Subject: below --
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
2025-01-09 13:46 Moakt Temporary Email
2025-01-10 3:24 ` Richard Stallman
2025-01-10 15:29 ` Björn Bidar
[not found] ` <87o70eptze.fsf@>
2025-01-16 0:06 ` Richard Stallman
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-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=s8djpJmsV7O7Rr2IBfgRIQsbtEd3TtUEYxCyXsjcg@localhost.localdomain \
--to=6bbf4f1ea5cc@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.