Automatic detection of ansi mode, so you can have a coloured login
screen.
On 23 Jun 2019, apam said the following...
Automatic detection of ansi mode, so you can have a coloured logi screen.
Curios, how do you autodetect?
Been doing lots of work on titan today.
Been doing lots of work on titan today.
I still have to get over there and check it out... :)
apam wrote to Black Panther <=-
I opened up my experimental BBS, it's at scratch.hopto.org 2023 or 2024 for telnet or ssh.
I am not sure why the filesystem does not exist. :)
apam wrote to Blue White <=-
I am not sure why the filesystem does not exist. :)
It needs at least gcc 8 to have the filesystem stuff in it.
On 23 Jun 2019, apam said the following...
Automatic detection of ansi mode, so you can have a coloured logi screen.
Curios, how do you autodetect?
Send a cursor position request and see if the client answers.
Andrew
Take it further Andrew! In PCBoard 16, I send 3 UTF8 characters - then
do the cursor position request. Non-UTF terminal returns cursor
position 10;1, whereas UTF8 terminal returns position 4;1
Re: Re: Titan Update
By: Ozz Nixon to apam on Tue Jun 25 2019 03:26 am
Take it further Andrew! In PCBoard 16, I send 3 UTF8 characters - then
do the cursor position request. Non-UTF terminal returns cursor
position 10;1, whereas UTF8 terminal returns position 4;1
Thanks, I'm gonna borrow that idea! :-)
On 2019-06-27 00:52:53 +0000, Digital Man -> Ozz Nixon said:
Re: Re: Titan Update
By: Ozz Nixon to apam on Tue Jun 25 2019 03:26 am
Take it further Andrew! In PCBoard 16, I send 3 UTF8 characters - then do the cursor position request. Non-UTF terminal returns cursor position 10;1, whereas UTF8 terminal returns position 4;1
Thanks, I'm gonna borrow that idea! :-)
Not a problem! I am trying to figure out how to detect terminal support
font changes - possible?
I know in VT mode some terminals will tell me their rows/cols, and can
be set to send resize notification - which I want to implement this
month, eg. ASAP if you can shed some light.
* Still tinkering with Kitty Protocol, for pixel and png support. (an
ANSI sequence).
'c')Not a problem! I am trying to figure out how to detect terminal support font changes - possible?
The SyncTERM/CTerm support for font changes can be queried using ANSI-like sequences http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/src/conio/cterm.txt
More specifically, I send a: "\x1b[0c" and then check the response for a compatible version of the CTerm library:
if(sscanf(p, "[=67;84;101;114;109;%u;%u", &x, &y) == 2 && *lastchar(p) ==
{
lprintf(LOG_INFO,"received CTerm version report: %u.%u", x, y);
cterm_version = (x*1000) + y;
if(cterm_version >= 1061)
autoterm |= CTERM_FONTS;
}
I don't know of any BBS terminals that will send unsolicited terminal size information. The closest thing I can think of is the Telnet "NEGOTIATE_WINDOW_SIZE" option, but that still is queried by the server and only works over Telnet (e.g. not SSH).
* Still tinkering with Kitty Protocol, for pixel and png support. (an
ANSI sequence).
Never heard of it. <shrug> I assume you're talking about this: https://sw.kovidgoyal.net/kitty/graphics-protocol.html
Interesting.
Re: Re: Titan Update
By: Ozz Nixon to apam on Tue Jun 25 2019 03:26 am
Take it further Andrew! In PCBoard 16, I send 3 UTF8 characters - then
do the cursor position request. Non-UTF terminal returns cursor
position 10;1, whereas UTF8 terminal returns position 4;1
Thanks, I'm gonna borrow that idea! :-)
digital man
On 2019-06-27 00:52:53 +0000, Digital Man -> Ozz Nixon said:
Re: Re: Titan Update
By: Ozz Nixon to apam on Tue Jun 25 2019 03:26 am
Take it further Andrew! In PCBoard 16, I send 3 UTF8 characters - then do the cursor position request. Non-UTF terminal returns cursor position 10;1, whereas UTF8 terminal returns position 4;1
Thanks, I'm gonna borrow that idea! :-)
digital man
I left an open question about SyncTerm's XModem Block Size(s)... but, I wanted to share this and see your thoughts.
I came across a Github ANSI post in some project, that they do
CSI 48;2;r;g;bm
CSI P$qm
ESC \
All as one string. And supposedly, ESC [ P $q m - is a "Did you under
stand the last 'm' sequence"... a reply containing
ESC [ 1 P (or was P 1) = YES
ESC [ 0 P (or was P 0) = NO
no response = NO
Have you see or implemented anything like that in SyncTerm?
As we could
use that to extend the UTF8 auto-detect, to also detect Client Side understood 256 Color Sequence, and then Client Side understood 24bit
Color Sequence... and then later focus on Client Side undersood Kitty Graphics Sequences, and Sound Sequences. At which point a BBS author
would know ANSI, ROWS/COLUMNS, CP437 or UTF8, ANSI Colors, and Graphics/Sounds... and of course for old school vector, RIP detection
too.
Where does SyncTerm store it's configuration file(s) on a Mac?
Re: Re: Titan Update
By: Ozz Nixon to Digital Man on Sun Jul 07 2019 10:10 pm
Where does SyncTerm store it's configuration file(s) on a Mac?
On my MacBook, it's in ~/Library/Preferences/SyncTERM/SyncTERM.ini
[Snipped]be
I have not. The full list of sequences supported by SyncTERM is supposed to
in this document: http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/src/conio/cterm.txt
Got a link to the project you're referencing?
SyncTERMAs we could
use that to extend the UTF8 auto-detect, to also detect Client Side understood 256 Color Sequence, and then Client Side understood 24bit
Color Sequence... and then later focus on Client Side undersood Kitty Graphics Sequences, and Sound Sequences. At which point a BBS author
would know ANSI, ROWS/COLUMNS, CP437 or UTF8, ANSI Colors, and Graphics/Sounds... and of course for old school vector, RIP detection
too.
It's an interesting concept. We added other query-type operations in
1.1 (e.g. for font support).
Deuce (deuce in #synchronet on irc.synchro.net) would be the one to really discuss escape sequences in detail.
Sysop: | Weed Hopper |
---|---|
Location: | Clearwater, FL |
Users: | 12 |
Nodes: | 6 (0 / 6) |
Uptime: | 09:56:20 |
Calls: | 67 |
Calls today: | 1 |
Files: | 50,165 |
D/L today: |
66 files (6,777K bytes) |
Messages: | 279,553 |