Zugg Software :: View topic - [3.34]xterm-related ansi bugs

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

1a)xterm sequences don't persist until that sequence is changed or the reset is encountered
1b)wrong color? (color 12--bright blue--is incorrect for background, not sure if there are other differences for other colors)

#print %e"[1;41mTe"%e"[1;34mst"

--the letters "Te" are colored as (whatever the foreground color happened to be) with a bright red background
--the letters "st" are colored bright blue on bright red

#print %e"[48;5;12mTe"%e"[38;5;12mst"

--the letters "Te" are colored as (whatever the foreground color happened to be) with a bright red background
--the letters "st" are colored as black background with bright blue background

2)xterm ansi sequences are not displayed in Script Debugger with ansi code options set (the ansi code is simply not included)
NOTE: this was relayed to me by Daern via Aardwolf chatter. The codes are sent and do appear in the Script Debugger, though Aard sends the standard-ansi sequence for the base 16 colors instead of the xterm format (it's also doing some visibility correction so I don't know if any sequence changes occur at those points either.)

3a)xterm ansi sequences are not included in clipboard pasting of ansi sequences in an ansi-trigger pattern textbox (the ansi code is simply not included)
3b)xterm ansi sequences cannot be triggered on via ansi trigger (probably related to what's causing 3a to occur)

4)still getting lots of ansi format bleed when doing frequent format-coded writes to a window without first clearing the window
RELATED: frequent clearing paired with writing causes flicker (doesn't look like the unintentional kind)
NOTE: this affects all vectors for applying formatting (raw ansi codes, %ansi(), #cw/color/etc, mxp). Still converting my strings, but at this point it appears that ansi use itself is way more severely affected by this than mxp or other methods.