On 9/23/21 3:54 AM, Thomas Dickey wrote:
More information...
Thank you Thomas. I will read and likely learn some new things as time
permits.
--
Grant. . . .
unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
On Wed, Sep 22, 2021 at 09:41:41PM -0600, Grant Taylor wrote:
> On 9/22/21 5:48 PM, Thomas Dickey wrote:
> > it does.
>
> Good.
>
> > The problem is that when I inverted the sense of the sixelScrolling
> > feature to address this:
> >
> > * invert the sense of DECSDM, to correspond with VT
On 9/22/21 5:48 PM, Thomas Dickey wrote:
it does.
Good.
The problem is that when I inverted the sense of the sixelScrolling
feature to address this:
* invert the sense of DECSDM, to correspond with VT382 manuals (lsix
#41).
Hum
I overlooked changing the compiled-in def
On Wed, Sep 22, 2021 at 10:17:30AM -0600, Grant Taylor wrote:
> On 9/22/21 10:16 AM, Grant Taylor wrote:
> > I'll reply with a copy of the Sixel image that I used for testing.
>
> Here's the Sixel of a TRON tank. Hopefully it comes through properly.
it does. The problem is that when I inverted
On 9/22/21 10:16 AM, Grant Taylor wrote:
I'll reply with a copy of the Sixel image that I used for testing.
Here's the Sixel of a TRON tank. Hopefully it comes through properly.
--
Grant. . . .
unix || die
Pq"1;1;640;400#0;2;0;0;0#1;2;19;25;25#2;2;38;44;44#3;2;25;0;0#4;2;60;0;0#5;2;85;0;0#
On 9/22/21 3:33 AM, Thomas Dickey wrote:
a script/testcase might help with this report.
1) Clear the screen.
2) cat a known good (and multiple text line tall) Sixel image.
3) Hit enter enough times to get the prompt down to the bottom of the
screen.
4) Repeat #2.
5) Compare the output fr
On Tue, Sep 21, 2021 at 07:12:55PM -0600, Grant Taylor wrote:
> I just tried xterm-369 and ran into a problem with Sixel support.
>
> It seems as if the Sixel starts at the home position, not at the current
> line like previous versions. What's worse is that the prompt will overwrite
> any part o
I just tried xterm-369 and ran into a problem with Sixel support.
It seems as if the Sixel starts at the home position, not at the current
line like previous versions. What's worse is that the prompt will
overwrite any part of the Sixel output that's below the current line.
E.g. if you clear
