From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Timothy <tecosaur@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: (Feature Request) customise LaTeX-preview regex
Date: Tue, 19 May 2020 09:26:33 +0200 [thread overview]
Message-ID: <875zcsl712.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <D161DA4C-A116-48F7-9D5E-3AB1DA4549B3@getmailspring.com> (Timothy's message of "Tue, 19 May 2020 09:59:37 +0800")
Hello,
Timothy <tecosaur@gmail.com> writes:
> This time, I'm wanting to be able to use the lovely org latex preview functionality for more than just the default blocks.
> For instance, I'm interested in applying it to mhchem \ce{ … }
> fragments, as well as siunitx \SI{ … }{ … }.
I think you can preview \ce{...} just fine, with appropriate LaTeX
headers.
> I thought modifying org-latex-regexps may do the trick, yet despite
> trying a few different things, I was confused when unable to get it to
> work. It looks like I'm being confounded by the fact that
> org-format-latex doesn't even reference org-latex-regexps, and instead
> uses it's own hard-coded regexps.
> Hopefully it may be possible to tweak this so that once can preview
> more than just the defaults hardcoded into org-format-latex.
This should not be possible. Org cannot recognize all LaTeX syntax. If
you cannot preview it, Org does not understand it. IOW, it would be
a poor experience if you preview something that doesn't exist, e.g.,
upon exporting the document.
OTOH, nothing prevents an external library to allow previewing any LaTeX
code (probably re-using AucTeX facilities).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2020-05-19 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 1:59 (Feature Request) customise LaTeX-preview regex Timothy
2020-05-19 7:26 ` Nicolas Goaziou [this message]
2020-05-19 7:49 ` Timothy
2020-05-19 11:45 ` Eric S Fraga
2020-05-19 14:27 ` Timothy
2020-06-14 13:53 ` TEC
2020-06-14 17:30 ` Nicolas Goaziou
2020-06-15 9:04 ` Eric S Fraga
-- strict thread matches above, loose matches on Subject: below --
2020-05-18 7:10 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=875zcsl712.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=tecosaur@gmail.com \
/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).