emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Diego Zamboni <diego@zzamboni.org>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: ox-* vs org-* naming convention?
Date: Sun, 7 Jun 2020 16:53:55 -0400	[thread overview]
Message-ID: <CAFyQvY02Jc77RLJL3DNaCqHrsQ6fVCYgkBwLhBJM0NfC5r=X3Q@mail.gmail.com> (raw)
In-Reply-To: <CAGY83EeU2653z==c0zauOAY5E9=AXeUf1rDPqtVvroprgqERnw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 243 bytes --]


This came up when I submitted ox-hugo to Melpa as well[1].

I stayed with the norm.. naming the package ox-hugo, but naming all the
functions and variables with org-hugo-* prefix.

[1] https://github.com/purcell/package-lint/issues/89

[-- Attachment #2: Type: text/html, Size: 471 bytes --]

  reply	other threads:[~2020-06-07 20:55 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 [this message]
2020-06-08  5:54 ` Jens Lechtenboerger
2020-06-08  6:57   ` Diego Zamboni
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

Reply instructions:

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 \
    --in-reply-to='CAFyQvY02Jc77RLJL3DNaCqHrsQ6fVCYgkBwLhBJM0NfC5r=X3Q@mail.gmail.com' \
    --to=kaushal.modi@gmail.com \
    --cc=diego@zzamboni.org \
    --cc=emacs-orgmode@gnu.org \


* 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).