Re: PATCH: query terminal properties on ZLE startup

[Oliver Kiddle <opk@xxxxxxx>]

Bart Schaefer wrote:
> On Tue, Feb 25, 2025 at 3:46 PM Oliver Kiddle <opk@xxxxxxx> wrote:
> >
> > In the current form, there's no setopt but you can disable it all with:
> >
> >   .term.extensions=( -query ).
>
> If I'm not mistaken, the terminal probe would take place during
> init_bltinmods() which happens before run_init_scripts() ?  So it's
> not actually possible to assign a value to .term.extensions before the
> terminal is probed at startup?

No, it's possible.
The queries take place at the point where the zle module is loaded.
That typically means the first bindkey or zle command in .zshrc. That
provides plenty of scope both to disable query extensions and to add
configuration that depends on the results of queries. I've checked
a --disable-dynamic build of zsh and that makes no difference - a
statically linked module is not setup before it's loaded. As far
as I can see, init_bltinmods() ends up calling autofeatures() on
behalf of the zle module with a features table for the two builtins I
mentioned plus vared. So zle isn't loaded at that point. If there's no
use of those builtins, it gets manually loaded with the first use of
the zleentry() function. I can find one use of that that may precede
run_init_scripts(): if you pass -o vi or -o emacs to zsh. If you think
that corner case is worth being concerned with, it'd probably work to
make ZLE check the option for the initial keymap choice when it loads
and remove the zleentry() call.

It's also possible that zle gets loaded from /etc/zshenv which would be
rather unhelpful. If you want to disable it, ~/.zshenv might be a good
choice.

Oliver