From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Name-space prefixes in ox- packages Date: Sat, 09 Sep 2017 12:09:11 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="089e082566b062d3d70558c09063" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34537) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dqeZj-0003Be-EV for emacs-orgmode@gnu.org; Sat, 09 Sep 2017 08:09:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dqeZi-0003tT-0V for emacs-orgmode@gnu.org; Sat, 09 Sep 2017 08:09:27 -0400 Received: from mail-yw0-x231.google.com ([2607:f8b0:4002:c05::231]:36574) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dqeZh-0003sK-Px for emacs-orgmode@gnu.org; Sat, 09 Sep 2017 08:09:25 -0400 Received: by mail-yw0-x231.google.com with SMTP id v72so11108926ywa.3 for ; Sat, 09 Sep 2017 05:09:23 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-org list --089e082566b062d3d70558c09063 Content-Type: text/plain; charset="UTF-8" Hello, I have observed that even though the exporter backend package names begin with ox-, all the variables and functions inside still start with org-. Is there a strong reason to do so? Or was that to prevent the older org-html, etc packages from breaking when they got renamed to ox-html, etc? So the question is if the new export backends should also follow the same convention. This question came up because if the ox- packages follow the convention used in core, they fail the lint check done by an external package called package-lint[1]. The lint checkers expects all variables and functions in a package FOO to have FOO- prefix. Here[2] the discussion on that package's GitHub issue thread. PS: I believe it is the same case with ob- packages. [1]: https://github.com/purcell/package-lint [2]: https://github.com/purcell/package-lint/issues/89 Thanks. -- Kaushal Modi --089e082566b062d3d70558c09063 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello,

I have observed that even though the exporter bac= kend package names begin with ox-, all the variables and functions inside s= till start with org-.

Is there a strong reason to = do so? Or was that to prevent the older org-html, etc packages from breakin= g when they got renamed to ox-html, etc?

So the qu= estion is if the new export backends should also follow the same convention= .=C2=A0

This question came up because if the ox- p= ackages follow the convention used in core, they fail the lint check done b= y an external package called package-lint[1]. The lint checkers expects all= variables and functions in a package FOO to have FOO- prefix. Here[2] the = discussion on that package's GitHub issue thread.=C2=A0

<= /div>
PS: I believe it is the same case with ob- packages.=C2=A0
<= div>

Thanks.=C2=A0<= /div>
--

Kaushal Modi

--089e082566b062d3d70558c09063--