From: Madhu <enometh@meer.net>
To: emacs-devel@gnu.org
Subject: Re: Possible minibuffer completion enhancements
Date: Wed, 24 Jan 2024 08:02:48 +0530 [thread overview]
Message-ID: <m35xzjwje7.fsf@leonis4.robolove.meer.net> (raw)
In-Reply-To: 87a5ox7png.fsf@daniel-mendler.de
* Daniel Mendler <87a5ox7png.fsf@daniel-mendler.de> :
Wrote on Mon, 22 Jan 2024 09:12:19 +0100:
> Iirc Stefan Monnier had plans to change the implementation of the
> completion machinery, rebasing it on a cl-defgeneric mechanism, where
> completion tables provide cl-defmethods. If more and more additional
> completion candidate metadata is supplied, looking into this again may
> be worthwhile.
Does this mean I have to restart emacs every time one has to undefine a
method? elisp has already disclaimed support any form of class
redefinition.
This is a disturbing trend that has been shepherded into emacs by Eli in
other areas too.
There was a comment in another thread about how COND* was a NIH reaction
to PCASE. I haven't seen stallman's response but I think problem is that
COND* was not invented first and is a shoving down on elisp of
constructs and patterns in languages that fundamentally are hostile to
lisp, and now elisp is being dragged down the path again.
Elisp implementations of cl-defclass and cl-defgeneric are deficient in
well understood ways. the campaign seems to drag the language of elisp
away from the freedom of lisp culture and replace that the culture with
a culture which shapes programmers who have been conditioned for a
different type of market which exploits that lack of freedom (through
derivative investments)
next prev parent reply other threads:[~2024-01-24 2:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 17:28 Possible minibuffer completion enhancements Eshel Yaron
2024-01-15 12:19 ` Eli Zaretskii
2024-01-16 13:47 ` Eshel Yaron
2024-01-16 14:10 ` Eli Zaretskii
2024-01-17 18:57 ` Eshel Yaron
2024-01-15 21:35 ` Stefan Kangas
2024-01-16 13:58 ` Eshel Yaron
2024-01-16 22:44 ` Stefan Kangas
2024-01-17 19:17 ` Eshel Yaron
2024-01-17 21:17 ` Stefan Kangas
2024-01-19 12:31 ` Eshel Yaron
2024-01-21 9:03 ` Eshel Yaron
2024-01-21 11:04 ` Daniel Mendler via Emacs development discussions.
2024-01-21 14:49 ` Eshel Yaron
2024-01-22 7:50 ` Juri Linkov
2024-01-22 8:12 ` Daniel Mendler via Emacs development discussions.
2024-01-22 12:18 ` Eshel Yaron
2024-01-22 12:35 ` Eshel Yaron
2024-01-23 8:08 ` Daniel Mendler via Emacs development discussions.
2024-01-22 20:31 ` Daniel Mendler via Emacs development discussions.
2024-01-23 7:04 ` Eshel Yaron
2024-01-23 8:00 ` Daniel Mendler via Emacs development discussions.
2024-01-23 16:23 ` Eshel Yaron
2024-01-23 18:32 ` Daniel Mendler via Emacs development discussions.
2024-01-24 2:32 ` Madhu [this message]
2024-01-22 21:11 ` Philip Kaludercic
2024-01-23 7:33 ` Eshel Yaron
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=m35xzjwje7.fsf@leonis4.robolove.meer.net \
--to=enometh@meer.net \
--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).