Thank you Thomas.
I'm now happily using XTerm 347 on Gentoo using the attached ebuild file
in a portage overlay.
It's a glorified copy of an earlier ebuild, renamed for the new 347 version.
--
Grant. . . .
unix || die
# Copyright 1999-2019 Gentoo Authors
# Distributed under the terms of the
On 7/12/20 5:31 PM, Thomas Dickey wrote:
Patch #358 - 2020/07/12
xterm-358 is working better than 357 did for me.
I tried 357 a few days ago and had problems, but wasn't able to dig into
it to find out why they were happening.
It seemed as if xterm wasn't acknow
On 7/13/20 1:59 AM, Thomas Dickey wrote:
There's always bugs to investigate, but a regression (new bug) really
ought to be fixed first.
To be clear, 356 worked, 357 failed, 358 works.
Do you still want a bug against 357? Or is it now obsolete?
--
Grant. . . .
unix || die
smime.p7s
Descr
On 7/13/20 4:12 PM, Thomas Dickey wrote:
I had a report against #357 yesterday; it's been obsoleted by #358.
That's what I figured.
(I'm working on a different program for the next few weeks, and
delaying a fix for something like this wouldn't be responsive).
I'm replying for completeness a
I just tried updating to xterm-365 and found that my answer back wasn't
working properly.
I found the same thing when I downgraded to xterm-364.
Ultimately I have stepped back to xterm-363 where I started.
I don't see any mention of anything related to answer back in either of
the announcemen
On 2/8/21 4:45 PM, Thomas Dickey wrote:
It's an incomplete fix:
Okay.
* correct/improve limit-checks for SRM versus ENQ from [372]patch
#344 (report by Tom Szilagyi).
From your standpoint it's a new bug, but that item was two bugs :-)
Meh. Things happen.
I'm revisiting this, to repa
On 2/10/21 3:38 PM, Thomas Dickey wrote:
Patch #366 - 2021/02/10
* improve fix for interaction between SRM and ENQ (report by Grant
Taylor).
Thank you Thomas.
I'm happy to report that xterm-366 seems to be working as well as
xterm-363 was. :-)
I've attached the ebuild file t
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
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 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
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 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 6/27/23 7:51 AM, Riza Dindir wrote:
I do not want to use a window manager for this.
As Carsten indicated, you probably /do/ /want/ a /Window/ /Manager/.
I suspect what you're really trying to avoid is a heavyweight /Desktop/
/Environment/.
DEs are a FAR BIGGER superset of and / or includ
On 6/28/23 4:35 PM, Chris Sorenson wrote:
That's not even possible anymore, it was way back in the day but now
X just immediately exits if there's no window manager to communicate
with,
Like Vito, I question the veracity of your claim.
I've not done it with a physical X11 (display) server in
On 7/21/23 8:18 PM, Michael K wrote:
I'm trying to connect an old HP logic analyzer (circa 1998) to a
modern Xorg server.
...
What might be the issue with this old X client authenticating with a
modern X server?
I would assume that `xhost +` would disable almost all security checking.
I'd c
On 7/22/23 4:05 AM, Carsten Haitzler wrote:
:1.0 (:1) is your problem i think. your X will be on :0 (port 6000).
the above error indicates it'd after something on :1 (port 6001).
also double check something is listening on 192.168.1.1 as opposed to
only on 127.0.0.1
I had wondered about th
On 7/22/23 3:47 PM, Michael K wrote:
To answer Grant's question. Yes, I had added the X ports but I've now turned
off the firewall just to be sure.
ACK
I generally don't like disabling the firewall. -- I'm currently
tilting at RPC for NFS to get it to work through a firewall.
But someti
On 2/7/25 07:38, Christophe Lohr wrote:
Then I can use it:
$ DISPLAY=localhost:1 xeyes
Try exporting the DISPLAY environment variable.
I've run into programs that do things that work with the variable
exported but don't work when it's not exported.
--
Grant. . . .
18 matches
Mail list logo
