I don't think you've considered how bad the design of the feature is.
If a program terminates by accident in the wrong state, other software
running afterwards is unaware that the session is behaving incorrectly,
and there are some dangerous conditions that a user cannot recover from.
(There are
There is a second layer of defense present: xterm can be configured at
runtime, through its disallowedWindowOps resource, to enable or disable
the SetSelection and GetSelection operations individually.
I think it would be more user friendly to have this feature compiled in,
but left disabled b
It is an extremely dangerous anti-feature.
>I observed that in OpenBSD 7.5, the configuration of xterm is such that
>xtermcfg.h gets #define OPT_PASTE64 0. A consequence of this is that
>OSC 52 support is compiled out, and a consequence of that is that tmux
>cannot set the primary X selection
Hello,
I observed that in OpenBSD 7.5, the configuration of xterm is such that
xtermcfg.h gets #define OPT_PASTE64 0. A consequence of this is that
OSC 52 support is compiled out, and a consequence of that is that tmux
cannot set the primary X selection (for copying text out of a tmux pane)
