From: Diego Zamboni <email@example.com>
To: Diego Zamboni <firstname.lastname@example.org>, Org-mode <email@example.com>
Subject: Re: ox-* vs org-* naming convention?
Date: Mon, 8 Jun 2020 08:57:53 +0200 [thread overview]
Message-ID: <CAGY83Ee-szSvq7zkv7DgP_j-BWPnjC8g00TXZgkTs9QkDsT=-Q@mail.gmail.com> (raw)
Hi Kaushal and Jens,
Thanks for your feedback, and also for the idea for the workaround
used in ox-re-reveal - that's a nice one :)
Given the special meanings of both the org- and ox- prefixes, I will
insist on keeping the current naming, and maybe take a stab at coming
up with a PR for https://github.com/purcell/package-lint/issues/89.
On Mon, Jun 8, 2020 at 7:54 AM Jens Lechtenboerger
> On 2020-06-07, Diego Zamboni wrote:
> > Hi,
> > I am working on submitting a new set of exporters I've been working on
> > (https://gitlab.com/zzamboni/ox-leanpub) to MELPA, and I received
> > feedback  about the discrepancy between the package names
> > (ox-leanpub-*) and the functions they define (org-leanpub-*). This is
> > also flagged by =package-lint=.
> >  https://github.com/melpa/melpa/pull/6942
> > [...]
> > I would appreciate any feedback about this - what are strong arguments
> > for or against insisting in this convention vs just adapting to the
> > rules suggested by package-lint?
> Hi there,
> for org-re-reveal, I use a small wrapper ox-re-reveal.el , whose
> commentary explains this:
> ;; Org export back-ends have file names starting with "ox-".
> ;; However, such files typically define variables and functions
> ;; starting with "org-", which causes errors by package-lint. To
> ;; define variables and functions with the usual prefix "org-" while
> ;; avoiding errors by package-lint, code is located in
> ;; org-re-reveal.el.
> ;; However, the prefix "ox-" is hard-coded in org.el and used to load
> ;; back-ends in `org-export-backends'. With this file, you can
> ;; customize `org-export-backends' and add `re-reveal'. Then, when
> ;; pressing `C-c C-e', this file will be loaded, which loads
> ;; org-re-reveal.el.
> Best wishes
>  https://gitlab.com/oer/org-re-reveal/-/blob/master/ox-re-reveal.el
next prev parent reply other threads:[~2020-06-08 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 16:30 ox-* vs org-* naming convention? Diego Zamboni
2020-06-07 20:53 ` Kaushal Modi
2020-06-08 5:54 ` Jens Lechtenboerger
2020-06-08 6:57 ` Diego Zamboni [this message]
2020-06-09 19:13 ` Diego Zamboni
2020-06-10 16:57 ` Diego Zamboni
2020-06-10 18:00 ` Kaushal Modi
2020-09-03 10:09 ` Bastien
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).