Hi Al, >>>>> Al Haji-Ali <abdo.haji....@gmail.com> writes: > I've now implemented everything over 6 commits (including the mentioned > refactoring) in my fork of auctex:
> https://github.com/haji-ali/auctex/tree/preview-point Thank you. > The configuration is similar to before, but is more incremental. [...] > ;; For instant frame display: > (setq buframe-update-debounce-delay 0)) ^ There is a spurious closing paren. > Let me know if you have any suggestions on improving code/interface or > if I made any mistakes in my implementation/documentations. Now the behavior with the suggested config is similar to the current standard preview-latex. That is, C-c C-p C-d turns the whole math expressions and section headers in the buffers into images, where the underlying LaTeX code appears only when the cursor enters the each image, Is this the intended behavior? > NOTE on dvisvgm: dvisvgm is my preferred way to view previews since, > unlike dvipng, it removes white-space around the preview, does not > suffer from pixelation and the face of the previews can be modified. > However, one problem with it is that it stops if one preview fails, > see here: https://github.com/mgieseki/dvisvgm/issues/293 > preview then uses dvips as backup which produces png images which is > quite jarring. The developer of dvisvgm seems open to "fixing" this > behaviour upstream. In the meantime, I wrote a small shell script that > simply re-invokes dvisvgm, skipping failed pages, which has the > desired effect (see issue above). OK. > On 05/09/2025, Arash Esbati wrote: > I agree with you regarding external dependencies. We can either: > - include it in auctex, as I do in my current fork. That would be completely > fine with me. > - Have it as an ELPA package, and have code in auctex that makes use of it if > the package is available (the two preview-point modes: after-string and > before-string, would still work without it) > - Or I can write extensible code that is buframe agnostic and leave it to the > user to make the necessary customization (I would make sure it's minimal). > My slight preference is to have buframe in a separate package in ELPA since I > plan to use it in other places, and it is not tex-specific. However, I am > happy with all three options. I'm fine with all three options. Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine #Gaza #StopMassiveKilling #CeasefireNOW
