[Pkg-xfce-devel] Bug#719228: Bug#719228: xfce4-terminal: Does not understand DECRQM, yet claims to be TERM=xterm
corsac at debian.org
Fri Mar 9 14:58:34 UTC 2018
control: reassign -1 libvte-2.91-0
control: affects -1 xfce4-terminal
On Fri, 2013-08-09 at 14:48 +0100, Paul Evans wrote:
> Package: xfce4-terminal
> Version: 0.6.2-3
> Severity: normal
> The DECRQM sequence (CSI ? ... $ p) is important for programs to be able
> to query the current settings of modes, either to be able to restore
> them after exit, or just to see what the settings are or probe for
> supported features.
> A real xterm responds to this. xfce4-terminal, while claiming to be an
> xterm (by setting TERM=xterm) does not; instead leaving unprocessed CSI
> output directly on the screen. I would copy-paste it here but I can't,
> because the output contains -literal- Escape bytes and that would upset
> vim, and possibly your mail client ;)
> The effect can be observed by
> $ echo -e '\e[?25$p'
> A terminal supporting DECRQM should reply something like:
> (which, since bash/readline don't understand the response, will just be
> printed raw into your next prompt line)
> xfce4-terminal however, raw-prints the query bytes, including the
> literal U+001B of the leading Escape byte, turning it into the little
> square-box pango substitution character.
> (Also it could be argued as a second bug that valid but unrecognised CSI
> sequences really ought to be stripped from the stream and not displayed
> as raw bytes of text; doubly-so should not be displayed with literal
> Escape characters in the terminal text buffer).
I somehow missed this bug, but terminal processing in xfce4-terminal is done
in libvte so I'm reassigning this bug there. I'm also adding the maintainers
to recipients so they get the initial mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: This is a digitally signed message part
More information about the Pkg-xfce-devel