Re: Clojure mode

[Philip Kaludercic]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  stefankangas@gmail.com,
>>   yandros@gmail.com,  bozhidar@batsov.dev,  dmitry@gutov.dev,  rms@gnu.org,
>>   danny@dfreeman.email,  emacs-devel@gnu.org,  manuel.uberti@inventati.org
>> Date: Tue, 29 Aug 2023 20:13:43 +0000
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > I think if we want to offer such a feature, we need first to come up
>> > with some friendly enough UI: when exactly to pop the suggestion, how
>> > to allow users to decline, how to install and configure if they say
>> > yes, etc.  Then there would be a need for some kind of DB with popular
>> > features that are not built-in and that people may wish to want; the
>> > challenge here is not to make the DB list too many features, otherwise
>> > we will be popping suggestions every single second...
>> 
>> How about splitting this into two separate tasks?  E.g. when a more
>> specific mode is found, a message is displayed in the minibuffer.  This
>> can occur once a session or once for every file.  The message would
>> instruct the user to invoke the appropriate command (e.g. a custom
>> command or by using the future history for `package-install').
>
> Something like that, yes.  But maybe there are other ideas?

Another idea might be to indicate that a package can be installed in the
mode-line.  If the user interacts with it, some the right package would
be installed, activated and enabled in the applicable buffers.

>> To make a concrete suggestion: The database would probably consist of
>> possible extensions to `auto-mode-alist', `magic-mode-alist' and
>> `interpreter-mode-alist'.
>
> That'd be the anchor, definitely, at least for major modes.  It could
> be a single function that is called if no suitable entry is found in
> any of these variables.

What could be a single function?

-- 
Philip Kaludercic