From: Timothy <orgmode@tec.tecosaur.net>
To: Matt Huszagh <huszaghmatt@gmail.com>
Cc: Ihor Radchenko <yantar92@gmail.com>,
sebastien.miquel@posteo.eu, emacs-orgmode@gnu.org
Subject: Re: [Patch] Align baseline of latex fragments and surrounding text
Date: Fri, 19 Jan 2024 17:33:03 +0800 [thread overview]
Message-ID: <874jf9pswx.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <CA+X8ke7e0_e5hL5-YhjPVjWgBDr9Fb64XHUi-Vwuj5-ucKP4LA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Hi Matt,
> However, I noticed that there appears to be another (large) patch in the
> works that also does this (email subject line “Overhaul of the LaTeX
> preview system”). That’s a long thread and I haven’t followed it. Is
> there still scope for my change? Is it worth getting this in?
So, in the large patch (actually ~150 patches in a branch), we actually
have had baseline alignment implemented for the last ~year 🙂.
Currently it’s just being polished up so it’s good to merge, you can see a list
of todo tasks we’d like to get sorted first here:
<https://github.com/tecosaur/org-latex-preview-todos/issues>
All the best,
Timothy
--
Timothy (‘tecosaur’/‘TEC’), 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/tec>.
prev parent reply other threads:[~2024-01-19 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 23:23 Patch to align baseline of latex fragments and surrounding text Matt Huszagh
2021-10-10 23:29 ` Matt Huszagh
2021-12-03 2:32 ` Matt Huszagh
2021-12-09 20:59 ` Sébastien Miquel
2021-12-09 22:18 ` Matt Huszagh
2021-12-10 15:49 ` Sébastien Miquel
2021-12-11 4:53 ` [Patch] Align " Matt Huszagh
2022-07-30 9:55 ` Ihor Radchenko
2024-01-19 6:41 ` Matt Huszagh
2024-01-19 9:33 ` Timothy [this message]
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=874jf9pswx.fsf@tec.tecosaur.net \
--to=orgmode@tec.tecosaur.net \
--cc=emacs-orgmode@gnu.org \
--cc=huszaghmatt@gmail.com \
--cc=sebastien.miquel@posteo.eu \
--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 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).