From: Ihor Radchenko <yantar92@posteo.net>
To: Matt Huszagh <huszaghmatt@gmail.com>,
Timothy <orgmode@tec.tecosaur.net>,
Karthik Chikmagalur <karthikchikmagalur@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Ihor Radchenko <yantar92@gmail.com>
Subject: Re: Patch to allow adjusting latex fragment display scale factor
Date: Fri, 19 Jan 2024 13:26:26 +0000 [thread overview]
Message-ID: <87v87po3nh.fsf@localhost> (raw)
In-Reply-To: <CA+X8ke6fXoDXqbqK5jgsMqesW_BO_Y7pBkYoACPUPCyRd+UnOg@mail.gmail.com>
Matt Huszagh <huszaghmatt@gmail.com> writes:
> Bringing this back up. Ihor, I've added you to the thread directly
> (hope that's ok).
>
> Any thoughts? I have not yet updated it for the most recent changes to
> main, but I can do that.
As you found in another thread, we have a WIP overhaul of the whole
LaTeX preview system. I hope that it can be merged in the coming few
months.
AFAIU, the new system will allow setting the scale factor - see
https://git.tecosaur.net/tec/org-mode/src/branch/dev/lisp/org-latex-preview.el#L57
Although, it does not look like a function is accepted as an allowed
value.
CCing Timothy and Karthik - they may have comments on the possibility to
allow function as :scale value.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-01-19 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 4:32 Patch to allow adjusting latex fragment display scale factor Matt Huszagh
2021-10-11 4:40 ` Matt Huszagh
2024-01-19 6:49 ` Matt Huszagh
2024-01-19 13:26 ` Ihor Radchenko [this message]
2024-01-22 5:11 ` Timothy
2024-01-22 5:26 ` Matt Huszagh
2024-01-22 9:47 ` Ihor Radchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v87po3nh.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=huszaghmatt@gmail.com \
--cc=karthikchikmagalur@gmail.com \
--cc=orgmode@tec.tecosaur.net \
--cc=yantar92@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.