From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jonas Bernoulli Newsgroups: gmane.emacs.devel Subject: Re: Adding transient to Emacs core Date: Tue, 20 Apr 2021 14:39:14 +0200 Message-ID: <87czupm8p9.fsf@bernoul.li> References: <87czuqi86o.fsf@bernoul.li> <83blaas1es.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33345"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Apr 20 14:44:34 2021 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 1lYpk2-0008ZV-DW for ged-emacs-devel@m.gmane-mx.org; Tue, 20 Apr 2021 14:44:34 +0200 Original-Received: from localhost ([::1]:33118 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lYpk1-0002Cg-9e for ged-emacs-devel@m.gmane-mx.org; Tue, 20 Apr 2021 08:44:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36788) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lYpez-0007UW-TV for emacs-devel@gnu.org; Tue, 20 Apr 2021 08:39:21 -0400 Original-Received: from mail.hostpark.net ([212.243.197.30]:58972) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lYpex-0007yf-Ot; Tue, 20 Apr 2021 08:39:21 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by mail.hostpark.net (Postfix) with ESMTP id B7DFE160F4; Tue, 20 Apr 2021 14:39:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bernoul.li; h= content-type:content-type:mime-version:message-id:date:date :references:in-reply-to:subject:subject:from:from:received :received; s=sel2011a; t=1618922354; bh=oGopDmPsmbw/z/wzVJ7SsG9b We0aP/+cGQOaMZTOAuM=; b=wHiZx3DUcjs4+qOzbrFzBFmOjAY/B6OYEryF2qp2 TBsG2lqBfm9Ncv9O3M4G/lAw7369A7Jh0KcUg81P1+GbxsTTxPnm2hAwjy6vCsn+ D6PxRv65Cijl8lMMCj7tFa4ki4Oblu/um5Upkjd2++UnRLC3u0n4dqDqGj4dZJ6a nRM= X-Virus-Scanned: by Hostpark/NetZone Mailprotection at hostpark.net Original-Received: from mail.hostpark.net ([127.0.0.1]) by localhost (mail1.hostpark.net [127.0.0.1]) (amavisd-new, port 10224) with ESMTP id 4ENb8vaOYZ4r; Tue, 20 Apr 2021 14:39:14 +0200 (CEST) Original-Received: from customer (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.hostpark.net (Postfix) with ESMTPSA id 885A4160EA; Tue, 20 Apr 2021 14:39:14 +0200 (CEST) In-Reply-To: <83blaas1es.fsf@gnu.org> Received-SPF: none client-ip=212.243.197.30; envelope-from=jonas@bernoul.li; helo=mail.hostpark.net X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:268201 Archived-At: Eli Zaretskii writes: >> So what do you think; should [we] proceed with this? > > Yes, please. Externally maintained packages are nothing new in Emacs; > see Org, for example. Should I just push this to master myself or open a ticket in debbugs? Should I add it as "lisp/transient.el" or "lisp/emacs-lisp/transient.el"? I'm also going to add this NEWS entry: > ** transient.el > > This library implements support for powerful keyboard-driven menus. > Such menus can be used as simple visual command dispatchers. More > complex menus take advantage of infix arguments, which are somewhat > similar to prefix arguments, but are more flexible and discoverable.