From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: epa command names Date: Sat, 12 Nov 2011 02:22:12 -0500 Message-ID: References: <87vcqpzw2w.fsf@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1321082545 15333 80.91.229.12 (12 Nov 2011 07:22:25 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 12 Nov 2011 07:22:25 +0000 (UTC) Cc: emacs-devel@gnu.org To: Thierry Volpiatto Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Nov 12 08:22:20 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RP7ut-0003FY-27 for ged-emacs-devel@m.gmane.org; Sat, 12 Nov 2011 08:22:19 +0100 Original-Received: from localhost ([::1]:32894 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RP7us-0003pu-8w for ged-emacs-devel@m.gmane.org; Sat, 12 Nov 2011 02:22:18 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:50762) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RP7up-0003pe-H8 for emacs-devel@gnu.org; Sat, 12 Nov 2011 02:22:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RP7uo-0002K9-8y for emacs-devel@gnu.org; Sat, 12 Nov 2011 02:22:15 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:34691 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RP7uo-0002K1-6T for emacs-devel@gnu.org; Sat, 12 Nov 2011 02:22:14 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAAEevk5FpZno/2dsb2JhbABBqi2BBoFyAQEEAVYjBQsLNBIUGA0kiBW2SIl/BIgQmW2ESA X-IronPort-AV: E=Sophos;i="4.69,498,1315195200"; d="scan'208";a="147644716" Original-Received: from 69-165-153-232.dsl.teksavvy.com (HELO ceviche.home) ([69.165.153.232]) by ironport2-out.pppoe.ca with ESMTP/TLS/ADH-AES256-SHA; 12 Nov 2011 02:22:12 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id 6AB2D660DC; Sat, 12 Nov 2011 02:22:12 -0500 (EST) In-Reply-To: <87vcqpzw2w.fsf@gmail.com> (Thierry Volpiatto's message of "Sat, 12 Nov 2011 07:36:07 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.91 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:146000 Archived-At: >>> I have switched to using epa instead of mailcrypt. The only drawback >>> I see is that the command names are not natural; thus, remembering >>> them is extra work. >>> Shall we give them aliases without `epa-'? For instance, define >>> `mail-encrypt' or `encrypt-mail' as an alias for `epa-mail-encrypt'? >> I don't much like this option because of the inability to handle >> conflicts. I'd much rather make M-x a bit more permissive such that M-x >> mail-encrypt falls back to epa-mail-encrypt (probably via completion). >> >> One way is something along the lines of the `substring' completion-style >> (which we could restrict to substrings that start after a word boundary), >> but I think we'd want something less general. >> >> I'm thinking of a way for packages to say "if `mail-encrypt' is matched >> by the user's input, then include `epa-mail-encrypt' in the list of >> completion candidates". This would handle conflicts very >> straightforwardly since if we have a second rule "if `mail-encrypt' is >> matched by the user's input, then include `superduper-mail-encrypt' in >> the list of completion candidates" M-x mail-encrypt TAB would simply >> provide both options as valid completion candidates. > anything does that actually. IIUC the "that" which it does is the "substrings that start after a word boundary" matching, but not the other one (which requires extra manually provided information, AFAICT). Right? Stefan