From: Timothy <firstname.lastname@example.org> To: Amin Bandali <email@example.com> Cc: Bastien Guerry <firstname.lastname@example.org>, email@example.com, Nicolas Goaziou <firstname.lastname@example.org>, Laszlo Elo <email@example.com> Subject: Re: ox-slimhtml Date: Mon, 04 Oct 2021 00:03:03 +0800 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1567 bytes --] Hi Amin, > What do you (other folks also) think? A while ago Nicolas forwarded me an email between him and Laszlo on this. Here are my thoughts at the time addresses to Laszlo (which haven’t changed much since): Nicolas <firstname.lastname@example.org> writes: > IIUC, merge is only viable if “ox-slimhtml” is a drop-in replacement for > “ox-html”. Otherwise, users will miss out many features. Of course, we > could ship two competing HTML export back-ends, but I don’t think that’s > a good idea either. > > So, it is meant for inclusion in Org proper, or as a GNU ELPA package? > I don’t know. Maybe Timothy has a clearer view about it. I believe I see your motivation in creating ox-slimhtml, as the current ox-html includes much more than could be considered strictly necessary. However, like Nicolas I am hesitant to put this straight into Org along side ox-html. My personal view is that ideally ox-html would be equipped with the relevant knobs and levers (metaphorically speaking) such that one could obtain the same result as ox-slimhtml, the current result, or something in-between. I’ve felt for some time that ox-html could benefit from a bit more in-built flexibility without going down the path of hooks, filters, and advice. This would certainly be more effort, so I completely understand if this isn’t something you’d like to undertake. In that case, I feel that this may be best suited as an ELPA package — closely in reach for those who are looking for a slimmer ox-html. All the best, Timothy
next prev parent reply other threads:[~2021-10-03 16:07 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 ` Timothy [this message] 2021-10-03 17:27 ` ox-slimhtml 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: 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: ox-slimhtml' \ /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
Code repositories for project(s) associated with this 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).