From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Proposal to change naming format to allow package-prefix/function-name Date: Mon, 30 Dec 2019 13:03:45 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000e11b27059aeaa478" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="239042"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Emacs developers To: Zachary Kanfer Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 30 13:04:40 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iltmq-00106O-Ew for ged-emacs-devel@m.gmane.org; Mon, 30 Dec 2019 13:04:40 +0100 Original-Received: from localhost ([::1]:60846 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iltmp-000700-8O for ged-emacs-devel@m.gmane.org; Mon, 30 Dec 2019 07:04:39 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41620) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iltme-0006zk-JJ for emacs-devel@gnu.org; Mon, 30 Dec 2019 07:04:29 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iltmc-00075w-Ge for emacs-devel@gnu.org; Mon, 30 Dec 2019 07:04:28 -0500 Original-Received: from mail-qk1-x731.google.com ([2607:f8b0:4864:20::731]:44595) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iltmb-00074v-5W for emacs-devel@gnu.org; Mon, 30 Dec 2019 07:04:26 -0500 Original-Received: by mail-qk1-x731.google.com with SMTP id w127so26069644qkb.11 for ; Mon, 30 Dec 2019 04:04:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=z575183EqByrbFQbOg15P8BwsGdft964kagI2xPP6Bc=; b=rz6PujsREAnN6GtkS4usy37BDYgUmkjWBHbs66c1B1+HAWR2AmnKgQtYvxZAbMYrH/ BQKKTfGXBQyr+gA4tGnri9Dgz+orMWXdQIvqY7/4uz2mVUJq06G8amKUgdziFkMMpgVa nrXT6yrIrykq1B+NS9urvY/kCpBwywmqSdUZybjNF2T1PbNfPQIKocPnje1st4lQzMwL sEsL2wqziL38yLr+56TXo6ryxdWz1pyz2tQzzv9ZbXCL8Ux89/Maz6OXlKsxlfDrI73e SvENGhBx25BBfQkKEmmq5Rgd3MqU64x+EDwPWX8AcdXUSuVJVj4KC1snyA6yQjUjMWKX qbvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=z575183EqByrbFQbOg15P8BwsGdft964kagI2xPP6Bc=; b=FIR40xsknGt70zj98wo27yPvz7L73aJPPpQ0c6oOJuAxNV402lf4taa+N5c3e4Vpt9 /qiF38vodMl4yrE1fthY5X34/xA7OVsgagNe9/+sdh21uSXSCgVa65azxn7SlnKrYzxJ ARIA8rhiIh8MmwnZqat8ooXqpM3VO2A0z1AwBTt7otASs3QE0m78LDjz5IAHrNrMKE16 LCmsPMQhVMTrTJ+JG9ttN78Cko2CHOL5nTuygh9z+AHBhsSeR3N1+ZO2r/vFKkqdGsqj Bh95BhiVyGEReNWzMR0Ck71c2aIQ5Tjj4XNMcgynEqGfyUrVljSKQdluGK1KT6cQBXBS 3mxA== X-Gm-Message-State: APjAAAUCfciZyBk8IFIImhYR3BAwjE392XrekZ6VtQcjw7WqWevuZrEy jaJKGWjjn8UsMGKyM3o9BksHr0A08ZuiavP1VrsorQ== X-Google-Smtp-Source: APXvYqxOi/WZdPHDZqKCCffkw+YgDg+3xAY3eBUjLiHqlkcsHq1+jk/vD/4pqlfmqwS26YyEgEP0jhSJ6jAglvK5SnY= X-Received: by 2002:a37:8ac4:: with SMTP id m187mr54070171qkd.277.1577707462792; Mon, 30 Dec 2019 04:04:22 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::731 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243767 Archived-At: --000000000000e11b27059aeaa478 Content-Type: text/plain; charset="UTF-8" On Mon, Dec 30, 2019 at 8:03 AM Zachary Kanfer wrote: > Some Elisp functions that are part of Emacs already follow this format. > 1. Many eshell functions already follow this format, for example eshell/ls, eshell/exit, and eshell/define. > 2. Pcomplete functions use this format, even some for more than one hierarchical level, e.g. pcomplete/gzip, pcomplete/erc-mode/complete-command, pcomplete/org-mode/block-option/src. > 3. Org-plot has half a dozen functions, like org-plot/goto-nearest-table. I think this proposal is unlikely to gain traction. But if it were, in a Lisp context colon (:) would make more sense IMHO, as it is used in Common Lisp to separate the namespace ("package", in CL-speak) from the symbol name. That would make easier to adapt to CL-style namespaces, if they were implemented in Emacs some day (which I think won't ever happen, if previous discussions on the subject are to be believed). --000000000000e11b27059aeaa478 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Mon, Dec 30, 2019 at 8:03 AM Zachary Kanfer <zkanfer@gmail.com> wrote:

&= gt; Some Elisp functions that are part of Emacs already follow this format.=
> 1. Many eshell functions already follow this format, for example e= shell/ls, eshell/exit, and eshell/define.
> 2. Pcomplete functions us= e this format, even some for more than one hierarchical level, e.g. pcomple= te/gzip, pcomplete/erc-mode/complete-command, pcomplete/org-mode/block-opti= on/src.
> 3. Org-plot has half a dozen functions, like org-plot/goto-= nearest-table.

I think this proposal is unlikely to gain traction. B= ut if it were, in a Lisp context colon (:) would make more sense IMHO, as i= t is used in Common Lisp to separate the namespace ("package", in= CL-speak) from the symbol name. That would make easier to adapt to CL-styl= e namespaces, if they were implemented in Emacs some day (which I think won= 't ever happen, if previous discussions on the subject are to be believ= ed).


--000000000000e11b27059aeaa478--