Package: console-tools Version: 0.2.3dbs-65 vcstime broken on console with a size of 256x128. It floods the screen with the time because it can't seek when it thinks the width is 0.
The problem is that /dev/vcsa stores the width in a single byte, so it reports my width as 0. vcstime then also thinks that my width is 0. There are a few solutions. One is to change number_of_columns() in vcstime.c to return an unsigned short, and make it return (rc[1]+256) if the number is less than 20 or so (to prevent impossible sizes). This will at least fix the flooding when it can't seek to any offset of the console, so this should be done regardless. A better, but harder, way is to use more well documented (and more correct) methods of finding the size than the second byte of the /dev/vcsa device. For example, the "resize" program correctly determines my width--that's how I found out it was 256 in the first place. I've also never had problems with any other programs like less, vi, emacs, or (e)links that require the width, so I suspect that their method of finding the width could be applied to vcstime. Debian: etch/testing Kernel version: 2.6.17.3 -Patrick __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
