#virtualterminals — Public Fediverse posts

There is a linux-16color terminal type in Dickey #terminfo. It has been there since 2009.

The #Linux KVT does not support more than the standard 8 colours, and some sleight of hand has been employed to get sort-of 16.

Unfortunately, the sleight of hand is broken.

If you've ever set TERM=linux-16colour and wondered at some strange scrolling and redraw artifacts, it is because the "op" capability doesn't undo the sleight of hand used by the setab/setaf capabilities.

#VirtualTerminals

There is a linux-16color terminal type in Dickey #terminfo. It has been there since 2009.

The #Linux KVT does not support more than the standard 8 colours, and some sleight of hand has been employed to get sort-of 16.

Unfortunately, the sleight of hand is broken.

If you've ever set TERM=linux-16colour and wondered at some strange scrolling and redraw artifacts, it is because the "op" capability doesn't undo the sleight of hand used by the setab/setaf capabilities.

#VirtualTerminals

There is a linux-16color terminal type in Dickey #terminfo. It has been there since 2009.

The #Linux KVT does not support more than the standard 8 colours, and some sleight of hand has been employed to get sort-of 16.

Unfortunately, the sleight of hand is broken.

If you've ever set TERM=linux-16colour and wondered at some strange scrolling and redraw artifacts, it is because the "op" capability doesn't undo the sleight of hand used by the setab/setaf capabilities.

#VirtualTerminals

@nixCraft

Of course, Apple showed us how to have buttons and frames and menus (and even a mouse pointer) on a text display many years ago, and Unicode 13 has made that system possible once again.

#MouseText #VirtualTerminals

This gave me an idea. Although the 8×8 fonts cannot be synthetically obliqued and boldfaced, because they are square, rectangular Ubuntu Mono can be.

So I can use #unscii PET for upright medium, unscii #BBCMicro for upright boldface, and #UbuntuMono for the oblique medium and boldface.

It works out fairly well.

#nosh #VirtualTerminals #vtfont

The 8×8 #BBCMicro font from #unscii works rather better than Ubuntu Mono does, when rendering virtual terminals to the framebuffer with console-fb-realizer, I think. And the PET font from unscii works better still.

#nosh #vtfont #VirtualTerminals

I can view the Japanese manual page for #yash (the Watanabe shell) in #FreeBSD.

It comes out as gibberish on kernel #VirtualTerminals. On user-space VTs it come out rather well. (This is what I want to screen grab.)

I fixed jfbterm and zhcon so that they work on FreeBSD again. Neither managed to display a UTF-8 Japanese manual page.

jfbterm is greeking everything, so just getting a font that works might well solve that. In zhcon the page comes out in the wrong encoding.

#framebuffer

I want to screenshot a user-space VT being realized on the framebuffer.

There are three framebuffer dump programs that I know of: fbdump, fbgrab, and fbshot. None of them work on #FreeBSD, because its framebuffer device works in a different way.

So writing a program to dump the frame buffer it is, then.

It looks like PBM files are the easiest output format.

#framebuffer #VirtualTerminals

I've just re-done some doco, based upon what's coming up in the next release. I posted screenshots of what this looks like, #MouseText and all, a little while ago.

I still have to physically resurrect the Debian development/test/build machine, with its dead hardware, before I can do a release. Those with GOPHER access can follow along, though, as the development source archive is up to date.

http://jdebp.info/Softwares/nosh/guide/virtual-terminal-login.html

#nosh #login #envuidgid #VirtualTerminals