unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Richard Stallman <rms@gnu.org>
Cc: Moakt Temporary Email <emacs-devel-proposal@drmail.in>,
	emacs-devel@gnu.org
Subject: Re: A new filter-based customization interface
Date: Tue, 24 Dec 2024 23:10:14 +0200	[thread overview]
Message-ID: <8530.70564787544$1735074676@news.gmane.org> (raw)
In-Reply-To: <E1tPwtI-0004mV-39@fencepost.gnu.org> (Richard Stallman's message of "Mon, 23 Dec 2024 23:51:32 -0500")

Richard Stallman <rms@gnu.org> writes:

> [[[ 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.

The website works entirely without JavaScript.
But there you go:
https://jpcdn.it/img/bde00610157f1ad327d8d066d5bc1744.png

> 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.

People promote non-free software all the on this list e.g. with
@gmail in their addresses or talk about non-free operating systems.
There's even a package solely to support non-free software in Elpa.

> 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.

Emails allow for attachments.

> 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?


The configure interface looks at times very old. I.e. in context of the
search it is very hard to see what the results actually are yes it does
show categories and settings items but it doesn't not show where they
are from e.g. as in which catergory a item is from or what tags it could
have.
I'm aware that Custom doesn't track tags but it is expected that most
system do use them or at least understand them for searching.

> 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.

The problem isn't eye-candy, functionality is the problem, e.g. in
discoverability. Improvements would help mostly beginner level users but
also long term users could benefit.
It does not help either that Emacs is not responding while searching.




  reply	other threads:[~2024-12-24 21:10 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
2024-12-24 21:10   ` Björn Bidar [this message]
     [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='8530.70564787544$1735074676@news.gmane.org' \
    --to=bjorn.bidar@thaodan.de \
    --cc=emacs-devel-proposal@drmail.in \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).