From: Ihor Radchenko <yantar92@posteo.net>
To: Niall Dooley <dooleyn@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] ox-beamer uses ox-latex private functions
Date: Sat, 23 Dec 2023 10:22:19 +0000 [thread overview]
Message-ID: <87cyuxqkv8.fsf@localhost> (raw)
In-Reply-To: <CADS3Lq7G9c+7+6TiizYQ9gzUA4=qi53Ht98XZ6fDGkqSF0pLOQ@mail.gmail.com>
Niall Dooley <dooleyn@gmail.com> writes:
> In three separate places (lines 779, 825 and 874) ox-beamer uses
> ox-latex private functions namely:
>
> line779: `org-latex--wrap-label'
> line 825: `org-latex--insert-compiler'
> line 874: `org-latex--format-spec'
>
> I appreciate ox-beamer is a backend backend derived from ox-latex but
> isn't this bad practice if these private functions were to change in
> future?
Both ox-beamer and ox-latex are parts of Org mode. So, there is nothing
wrong with using these internal functions - we have the control over all
parts of Org mode. If we decide to make a breaking change in any
internal function in Org mode, its users in Org source code must be
changed; be it the same file or not.
Not a bug.
Canceled.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-12-23 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 21:21 [BUG] ox-beamer uses ox-latex private functions Niall Dooley
2023-12-23 10:22 ` Ihor Radchenko [this message]
2023-12-23 17:43 ` Niall Dooley
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87cyuxqkv8.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dooleyn@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).