From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: PROPOSAL: Repurpose one key (why only one?) and reserve it for third-party packages Date: Sun, 14 Feb 2021 22:24:42 +0300 Message-ID: References: <87ft20f3ec.fsf@posteo.net> <8735xz67ye.fsf@posteo.net> <87mtw74j5h.fsf@posteo.net> <663841c0e3fb003a733c@heytings.org> <663841c0e31fdd6c8e1e@heytings.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6450"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Cc: help-gnu-emacs@gnu.org To: Gregory Heytings Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sun Feb 14 20:27:01 2021 Return-path: Envelope-to: geh-help-gnu-emacs@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 1lBN2q-0001XK-4v for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 14 Feb 2021 20:27:00 +0100 Original-Received: from localhost ([::1]:55878 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lBN2p-0006zQ-6n for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 14 Feb 2021 14:26:59 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52642) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lBN27-0006wm-Ni for help-gnu-emacs@gnu.org; Sun, 14 Feb 2021 14:26:15 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:43173) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lBN26-0008KF-4E for help-gnu-emacs@gnu.org; Sun, 14 Feb 2021 14:26:15 -0500 Original-Received: from localhost ([::ffff:41.210.147.95]) (AUTH: PLAIN securesender, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 000000000001E1BF.0000000060297952.00002D03; Sun, 14 Feb 2021 12:26:09 -0700 Mail-Followup-To: Gregory Heytings , Drew Adams , help-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <663841c0e31fdd6c8e1e@heytings.org> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:128052 Archived-At: * Gregory Heytings [2021-02-14 21:58]: > > > > I agree with Drew that the solution you propose is not user-friendly, > > > > Huh? AFAIK, I've said nothing about what you guys seem to be talking > > about now. Please cite what you think I said about this, if you're > > going to make references to what I've said. > > > > See: > > Date: Sat, 13 Feb 2021 20:48:11 +0000 > Message-ID: > > in which you said: > > > > Philip Kaludercic suggested some code for prompting users before > > > mapping keys. I think that's a good idea. > > > > Maybe that could be part of a solution. But many users will not > > appreciate, or not be prepared for, making such key-binding decisions at > > the outset and on the fly. It can be easily solved by introducing variable `ask-me-for-packages-which-need-prefix-key' which is by default NIL. Packages can then notify Emacs that they need one or more prefix keys: (need-prefix-key 'my-package-map-1) (need-prefix-key 'my-package-map-2) Emacs would then provide the unified wizard function that asks those users who have set the above variable for prefix keys for the package. That solves universally those hypothetical problems discussed.