bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

console strikes again


From: Marcus Brinkmann
Subject: console strikes again
Date: Tue, 10 Sep 2002 04:19:02 +0200
User-agent: Mutt/1.4i

Hi,
here your "daily" report on console progress.

* scrollback works in the VGA client.  You can scroll back half pages with
  RightShift+PageUp and RightShift+PageDown, and you can scroll back by line
  with LeftAlt+CursorUp and LeftAlt+CursorDown.

  The scrolling behaviour is more like an xterm rather than the Linux
  console.  If you have scrolled up, the visible region is "sticky", even if
  there is more output appended on the console or something interested
  happens further down.  So, it is really like a panning window you can move
  over the whole buffer size.  If you are at the top of it, the whole buffer
  is used, and there is more output appended, there is no way to avoid the
  scrolling though (the trick is to prevent output from being appended by
  pressing ^S if you want to make sure that it stays still.)

  I want to add here that calculating a clipping region sucks.  This will
  get very interesting when cut&paste support is added.

* A real timer.  The beep is now really 1/10 sec long on all systems, unless
  the timer thread is not scheduled timely, of course :)
  The timer is ripped and beautified from pfinet.  It allows any driver to
  do something on time, like screen blanking etc.  This will be very useful
  and important, so I implemented it now.

* VGA flashing.  To try it out, echo `tput flash`.  This is the visible
  bell.  What flashes is the border color from black to white for 1/10 sec.

* New options --driver-path and --driver.  I start it like this:

$ LD_LIBRARY_PATH=../libcons ./console-console --driver-path . \
  --driver vga --driver pc_kbd --driver pc_speaker /dev/vts

I would like to pass intermediate arguments (--driver vga --many-glyphs etc)
to the drivers, but I have not figured out how to do this safely.  Maybe I
need to copy the args until the next --driver, and you will then have to
specify the /dev/vts either with --console or using --.

This is all I can remember now.  Have fun!

Thanks,
Marcus


-- 
`Rhubarb is no Egyptian god.' GNU      http://www.gnu.org    address@hidden
Marcus Brinkmann              The Hurd http://www.gnu.org/software/hurd/
address@hidden
http://www.marcus-brinkmann.de/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]