Skip to contentSkip to conversation

/dev/vcs: stuck with dimensions <255?

DISCUSSION Samuel Thibault 1 participant 1 message Aug 6, 2004 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Le mar 30 sep 2003 à 11:10:11 +0200, Mario Lang a tapoté sur son clavier :

Quoted 7 lines

I just realized, that /dev/vcsa behaviour is broken when used with lines or columns more than 255. I can easily get this behaviour by using the built-in 4x6 font on a 1024xsomething resolution. That results in 256 columns. However, the vcs devices expose dimensions and cursor position in the first 4 bytes.

Quoted 7 lines

My question is now: Are we stuck with this now? I found that it is at least possible to use TIOCGWINSZ on the corresponding /dev/tty%d device to get correct dimensions, but then again, how would I optain the cursor position?

I am wondering why a char was choosen at all. I see no gain by "saving" space there...

Well, vcsa was added a long time ago, I guess such dimensions weren't possible at that time.

Of course we aren't stuck: we just need to add /dev/vcsx* which would hold 32-bits integers, hoping this is sufficient once for all...

Regards,
Samuel