Hi Arash, Arash Esbati <[email protected]> writes:
> Al Haji-Ali <[email protected]> writes: > >> By design. See `preview-auto-reveal`. I set it to `t` to have the >> preview always "autoopen". > > Thanks, I should have consulted the manual first. I see I can also add > > (key-binding [up]) > (key-binding [down]) > > to `preview-auto-reveal-commands' in order to get what I'm looking for. > > @Paul: Is there a reason why you didn't add these 2 keys to > `preview-auto-reveal' when you expanded the default with commit > 06c0df55? The defaults I added (pop-to-mark-command, undo) seemed uncontroversial, but the convention of auto-revealing on horizontal but not vertical motion goes back quite a ways (c2bdc736). I assumed this was because horizontal motion conveys deliberate intent to cross a boundary, whereas vertical motion might just land on a preview incidentally. P.S. I do include equivalent commands (previous-line and next-line) in my own customization of this option: (tex-parens-backward-down-list tex-parens-down-list czm-tex-jump-back-with-breadcrumb end-of-buffer beginning-of-buffer previous-line next-line consult-register-load ace-window other-window flymake-goto-prev-error flymake-goto-next-error (key-binding [left]) (key-binding [right]) backward-char forward-char pop-to-mark-command undo) _______________________________________________ bug-auctex mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-auctex
