emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: chris <inkbottle007@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-latex-preview with custom sty file
Date: Fri, 24 Feb 2023 19:29:16 +0100	[thread overview]
Message-ID: <8227477.NyiUUSuA9g@pluto> (raw)
In-Reply-To: <87edqfne9t.fsf@tec.tecosaur.net>

On Friday, 24 February 2023 18:49:10 CET Timothy wrote:
> Hi Chris,
> > Note: I haven’t been able to compute the return value of the hash function for
> > my latex expression, because I can’t figure out what the arguments actually are,
> > specifically `forbuffer`, `fg` and `bg`, but the above reasoning seems sound.
> > Note: Removing specifically the images looking like the image associated with
> > the latex expression that refuses to be regenerated, using some file manager,
> > and then invoking `org-latex-preview`, does the trick, but it’s impractical.
> Yea, `org-format-latex' is a bit of a nightmare. I’ve got a WIP overhaul of the
> entire LaTeX preview system which is currently 95% of the way done. The new
> system will still not notice changes in package source files, but it will be
> easy to clear the cache and regenerate.

There is that, which is supposed to be included in org-mode 9.7:

I suppose for image regeneration it needs user manual intervention, otherwise it's the same to do `rm ltximg/*`.

If I were able to compute the output of the hash function I could have decided which image to selectively remove.

> All the best,
> Timothy

      reply	other threads:[~2023-02-24 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 17:25 [BUG] org-latex-preview with custom sty file chris
2023-02-24 17:49 ` Timothy
2023-02-24 18:29   ` chris [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:

  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=8227477.NyiUUSuA9g@pluto \
    --to=inkbottle007@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).