From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Adam Porter Newsgroups: gmane.emacs.devel Subject: Re: library prefixes (versus other name prefixes) Date: Sun, 03 May 2020 10:07:39 -0500 Message-ID: <87r1w16oqs.fsf@alphapapa.net> References: <73dcba36-03d1-408e-84ac-b07edde8ef77@default> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="15887"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun May 03 17:08:19 2020 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 1jVGE7-00042k-IG for ged-emacs-devel@m.gmane-mx.org; Sun, 03 May 2020 17:08:19 +0200 Original-Received: from localhost ([::1]:42784 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jVGE6-0000Us-Kv for ged-emacs-devel@m.gmane-mx.org; Sun, 03 May 2020 11:08:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46950) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVGDe-0008Ul-ML for emacs-devel@gnu.org; Sun, 03 May 2020 11:07:50 -0400 Original-Received: from ciao.gmane.io ([159.69.161.202]:59632) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jVGDd-0004Eh-UJ for emacs-devel@gnu.org; Sun, 03 May 2020 11:07:50 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1jVGDb-0003XO-2s for emacs-devel@gnu.org; Sun, 03 May 2020 17:07:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=159.69.161.202; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/03 11:07:47 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN 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:248700 Archived-At: If I may offer a perspective from "MELPA land" (though I am not MELPA, just a contributor): MELPA has not always required that submitted packages strictly adhere to the Elisp manual's conventions, so some older packages do use a slash as a prefix separator. New packages are frequently submitted which use a slash separator. Now, MELPA requires them to replace the slash with a hyphen, as the Elisp manual recommends. Sometimes the package authors are very reluctant to do so. Some built-in Emacs packages also use a slash separator, like pcomplete (although it seems to use it only for generated completion functions, not library functions). Some MELPA packages also use a colon as a separator, like Hydra (although, like pcomplete, it seems to use it only for generated Hydra functions). In my own non-MELPA code, I use a slash separator. For me, it's more visually distinctive than a hyphen and makes it easier to discern the prefix part of the symbol. So, I would be glad if the official Elisp conventions allowed a slash separator, and I think many other Elisp package authors would as well. This topic frequently comes up in discussion on reddit.com/r/emacs, which is read by many users and package authors, so I've linked this thread there: https://old.reddit.com/r/emacs/comments/gcrwic/the_symbolprefixseparatormustbeahyphen_topic/