On 03/11/2025, Paul D. Nelson wrote:
> I may have added to the confusion by writing "construction symbol" (what
> shows up when a preview is regenerating) in a few places where I should
> have written "TeX symbol" (what shows up when the TeX source is made
> visible after point enters a preview).

Ah this is finally becoming clear to me. Sorry it took a while and I
thank you for your patience.

> I don't think I'm proposing to introduce more modes of operation.  I'm
> just observing that preview-point bundles two orthogonal features: (a)
> disabling preview display by default, and (b) richer customization of
> how to display the preview at point.  Feature (b) would be useful even
> without feature (a), so it seems worth decoupling the two and allowing
> them to be configured separately.  Does that clarify what I had in mind?

I largely agree with you, and I am happy for finer control over the
behaviour to be added.

The new mode of operation I was referring to is when
`preview-display-style` is set to 'preview (so that previews away from
point are displayed) and `preview-reveal-display` is `buframe`.

Presumably the previews away from the cursor are being shown using the
'display' property of the overlay (as is currently done). When the
cursor opens the preview, I think you are proposing that the TeX source
is displayed in the buffer (by setting 'display to nil) while the
preview *moves* to a buframe. When the cursor moves out of the source,
the preview moves back into the buffer as a 'display property, correct?
If so, don't you think previews moving between buframe and main buffer
would be jarring? I am also still unclear what happens in this case when
the TeX source is modified. Does the preview return back to the buffer
as a 'display property or does the TeX source remain visible (I'd guess
the latter is more reasonable)?

In any case, if my understanding is correct, this would require new,
careful implementation of moving the preview back and forth.

Best regards,
-- Al



_______________________________________________
bug-auctex mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-auctex

Reply via email to