From: Bastien <bzg@gnu.org>
To: Amin Bandali <bandali@gnu.org>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>,
Laszlo Elo <hello@bald.cat>
Subject: Re: ox-slimhtml
Date: Sun, 03 Oct 2021 19:27:51 +0200 [thread overview]
Message-ID: <875yue3tns.fsf@gnu.org> (raw)
In-Reply-To: <87ilyeje9r.fsf@gnu.org> (Amin Bandali's message of "Sun, 03 Oct 2021 11:53:36 -0400")
Hi Amin,
Amin Bandali <bandali@gnu.org> writes:
> Bastien, would you and Nicolas be open to adding ox-slimhtml more or
> less in its current form to Org core, if Laszlo, myself, and/or others
> look after it and help maintain it?
No, because it would be confusing to have two HTML export backends in
Org's core.
BTW, https://github.com/balddotcat/ox-slimhtml says "slimhtml is now
part of Org, included in GNU Emacs, future bug reports or
contributions should be sent to Org directly" ... which is wrong, and
I can't fill a bug report because the repo is archived.
Elo, are you still working on it?
From what I've read in previous discussions, I believe I'm in line
with Nicolas and Tim on this: we can probably enhance ox-html.el by
following some design goals that ox-slimhtml.el have set, and leave
other decisions aside, because ox-html has to stay as generic as
possible.
In any case, I'd rather have Elo work with Tim on enhancing ox-html
than to allow another package in Org's core.
If ox-slimhtml is still maintained, it can for sure live in GNU or
NonGNU ELPA.
WDYT?
--
Bastien
prev parent reply other threads:[~2021-10-03 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 5:48 ox-slimhtml Laszlo Elo
2020-12-14 9:07 ` ox-slimhtml tomas
2020-12-16 11:45 ` ox-slimhtml Bastien
2021-09-25 15:50 ` ox-slimhtml Bastien Guerry
2021-10-03 15:53 ` ox-slimhtml Amin Bandali
2021-10-03 16:03 ` ox-slimhtml Timothy
2021-10-03 17:27 ` Bastien [this message]
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=875yue3tns.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=bandali@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=hello@bald.cat \
--cc=mail@nicolasgoaziou.fr \
/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).