Hello Paul,
Apologies, there's something I don't fully understand. Below is an
attempt at explaining what I currently understand.
On 02/11/2025, Paul D. Nelson wrote:
>
> - just the construction symbol and the tex code (default behavior in
> AUCTeX)
>
> - the preview before the tex code (current behavior of
> preview-leave-open-previews-visible t)
> - the preview after the tex code
My understanding of the `preview-leave-open-previews-visible` option is
that the previews remain open only when the tex code is changed rather than
being replaced with a sign. If the tex source is not changed, the
previews are not kept open. In particular, this shouldn't affect the
position of the image AFAIK.
So, I assume then that you don't mean changing the traditional preview
style after all? But rather have a mode which always show the preview
before or after the tex source with the point movement not affecting
previews.
> - a buframe showing the preview
This has to be point-specific, otherwise it would require showing too
many frames and I don't think it would look good to always show and move
them around.
In summary, here are the behaviours we can have:
- classical preview, before-string (open on cursor going inside image).
- classical preview, after-string (open on cursor going inside image) -- New,
needed?
- preview-point with {after,before}-string or buframe.
- a new mode where previews are not affected by cursor movement, and
previews are always shown as {before,after}-string.
If my understanding is correct of your proposal, then indeed one can have two
options, let's say:
- preview-display: 'preview, 'src, 'both
- preview-display-style: 'after-string, 'before-string, 'buframe
with 'buframe being only supported when `preview-display` is `'src`.
Here:
- preview-display='src is the preview-point style.
- preview-display='preview: is the current preview style.
- preview-display='both: is the new style you want where both source and
preview are always shown and point movement does not affect them.
If my understanding is correct, it shouldn't be too difficult to implement
these, I think.
Best regards,
-- Al
_______________________________________________
bug-auctex mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-auctex
