From: Timothy <tecosaur@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: About exporting
Date: Thu, 01 Apr 2021 21:25:38 +0800 [thread overview]
Message-ID: <87v996dtm5.fsf@gmail.com> (raw)
In-Reply-To: <87czve1bom.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Thursday, 1 Apr 2021 at 16:50, Timothy wrote:
>> I think in part this works for me because of a particular system I
>> have in place (that IMHO works *wonderfully* with Org) which I plan on
>> submitting patches to upstream (to Org) in the not-to-distant future.
>
> Interesting. Look forward to seeing this!
If you want to get an "sneak peek" you may be interested in taking a
quick look at:
https://tecosaur.github.io/emacs-config/config.html#content-feature-preamble
In essence this system is the combination of LaTeX snippet / generated
content with feature detection.
For example, this is what I have for working with Julia code:
#+begin_src emacs-lisp
(add-to-list 'org-latex-conditional-features '((and org-export-has-code-p "^[ \t]*#\\+begin_src julia\\|^[ \t]*#\\+BEGIN_SRC julia\\|src_julia") . julia-code) t)
(add-to-list 'org-latex-feature-implementations '(julia-code :snippet org-latex-julia-mono-fontspec :order 0) t)
(add-to-list 'org-latex-feature-implementations '(.microtype-lualatex :eager t :when (microtype julia-code) :prevents microtype :order 0.1 :snippet "\\usepackage[activate={true,nocompatibility},final,tracking=true,factor=2000]{microtype}\n"))
(add-to-list 'org-latex-feature-implementations '(.custom-font-no-mono :eager t :prevents custom-font :order 0 :snippet (org-latex-fontset :serif :sans)) t)
#+end_src
It's been evolving for a several weeks now, and I feel like it should
soon settle down enough that I will be happy preparing a patch based on
it.
--
Timothy
next prev parent reply other threads:[~2021-04-01 13:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.51.1617033608.26133.emacs-orgmode@gnu.org>
2021-03-29 19:37 ` About exporting Ypo
2021-03-29 20:15 ` William Denton
2021-03-29 20:46 ` autofrettage
2021-03-29 21:39 ` Samuel Wales
2021-03-29 21:31 ` Juan Manuel Macías
2021-03-29 22:06 ` Tim Cross
2021-03-30 6:17 ` Eric S Fraga
2021-03-30 8:01 ` Colin Baxter
2021-03-30 8:13 ` Detlef Steuer
2021-03-30 10:15 ` Eric S Fraga
2021-03-30 11:40 ` Joost Kremers
2021-03-30 8:17 ` Eric S Fraga
2021-03-30 11:04 ` Juan Manuel Macías
2021-03-29 22:26 ` Thomas S. Dye
2021-03-30 4:47 ` Greg Minshall
2021-03-30 11:54 ` Martin Steffen
2021-03-30 12:44 ` autofrettage
2021-03-30 14:35 ` Martin Steffen
2021-03-30 14:44 ` autofrettage
2021-03-30 15:44 ` Juan Manuel Macías
2021-03-31 9:59 ` Eric S Fraga
2021-03-31 18:28 ` Martin Steffen
2021-04-01 6:52 ` Eric S Fraga
2021-04-01 7:00 ` Tim Cross
2021-04-01 7:29 ` Eric S Fraga
2021-04-01 8:50 ` Timothy
2021-04-01 11:33 ` Eric S Fraga
2021-04-01 13:25 ` Timothy [this message]
2021-04-02 14:06 ` Eric S Fraga
2021-04-01 14:21 ` Juan Manuel Macías
2021-03-30 20:49 ` Tim Cross
2021-03-31 18:56 Juan Manuel Macías
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=87v996dtm5.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).