From: Timothy <tecosaur@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: (Feature Request) add more entry points to configure some export functionality
Date: Mon, 18 May 2020 14:58:12 +0800 [thread overview]
Message-ID: <602097E9-CA33-4F79-AC8A-0061E99A306D@getmailspring.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
It's me again!
We're now onto email 2/4. This one is a wish-list of entry points for customising export functionality (well, styling).
I'm a big fan of trying to make my documents look snazzy with minimal work (i.e. by cramming all the snazzyness in the back-end), which is why I was thrilled to be able to make use of customisations like org-html-checkbox-types (see https://tecosaur.github.io/emacs-config/config.html#change-checkbox-type for my use of it).
However, there are a two areas where I am really interested in seeing similar customisations, ideally without the need to advice-override org functions. In the hope that these may be developed, I'll detail them below.
LaTeX Export: Checkboxes
- I also want to be able to tweak the checkboxes here.
HTML Export: Headers
- I'd quite like to customise the generation of headers
This is with the aim of adding the rather nice github-style 🔗 to easily copy a link to that position to the clipboard.
From memory modifying this would require overriding a large function, which I didn't like the look of.
Best wishes,
tecosaur
[-- Attachment #2: Type: text/html, Size: 1477 bytes --]
next reply other threads:[~2020-05-19 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 6:58 Timothy [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-19 1:58 (Feature Request) add more entry points to configure some export functionality Timothy
2020-05-19 7:31 ` Nicolas Goaziou
2020-05-19 8:54 ` Timothy
2020-05-19 9:29 ` Nicolas Goaziou
2020-05-19 12:50 ` Timothy
2020-05-19 13:17 ` Nicolas Goaziou
2020-05-19 13:23 ` Timothy
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=602097E9-CA33-4F79-AC8A-0061E99A306D@getmailspring.com \
--to=tecosaur@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).