From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Clojure mode Date: Wed, 30 Aug 2023 14:11:51 +0300 Message-ID: <83il8whjig.fsf@gnu.org> References: <87il9kksqz.fsf@dfreeman.email> <87cyzrjbd8.fsf@dfreeman.email> <83zg2vav46.fsf@gnu.org> <87o7j99304.fsf@dfreeman.email> <87zg2hsyrd.fsf@dfreeman.email> <87h6ontwfv.fsf@posteo.net> <4874df51-9652-f9fd-0576-9dd6a4cba31a@gutov.dev> <3d5ef276-ce6b-9ff0-0c60-1da6b887b365@gutov.dev> <1070e416-2a13-49e0-90d4-fbc526cd461c@app.fastmail.com> <83ttskia84.fsf@gnu.org> <97c96b72-ebba-4853-98d2-86e3ba8bbc05@app.fastmail.com> <83sf84i9ix.fsf@gnu.org> <837cpfhzdm.fsf@gnu.org> <83zg2agjp8.fsf@gnu.org> <87ttshk3ns.fsf@posteo.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4441"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 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 To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 30 13:13:43 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qbJ8o-0000xN-M3 for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Aug 2023 13:13:42 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qbJ7l-0006Rp-1y; Wed, 30 Aug 2023 07:12:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qbJ7j-0006RA-KW for emacs-devel@gnu.org; Wed, 30 Aug 2023 07:12:35 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qbJ7h-0004G9-LU; Wed, 30 Aug 2023 07:12:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=o3Fse/EJQq1eResGBjWtwA8JJJMhmiwf+ld037yVVHI=; b=eD3mwe0fuP5E yJM4AvoqUcxkljhVJxNka6NHVVHTn9YGvYJX04qBfjgP3J7AlLvlCU6OMB1gCfydFSBby3OZ05Ssq q3ycfW+PdQQYRzLX2cRaJDKzQIzy5UlNtIcU4++FSrvtX2ErRF7HQSSop+VeZJxVjr2kPKfRB4JDG 8laNTbgu6iYzBy6yK4e69J9V9CJdo9QoqhSh3OM99A7izBdXk2JpkXVZIoLNC+l/xFWf3atSppO4H 6efvB6yi0W052PTXAWCoxv8K0Uv02gGqaIRJr+KJ4xxp2yD33LMxj8mex0NThasfLR0ny2kh8hPLZ bPHqY36sYYgazxsRNTVtDQ==; In-Reply-To: <87ttshk3ns.fsf@posteo.net> (message from Philip Kaludercic on Tue, 29 Aug 2023 20:13:43 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:309540 Archived-At: > From: Philip Kaludercic > Cc: Stefan Monnier , 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 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? > 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.