[Top][All Lists]

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

Re: console-client close to initial check in

From: Marcus Brinkmann
Subject: Re: console-client close to initial check in
Date: Sat, 14 Sep 2002 02:08:44 +0200
User-agent: Mutt/1.4i

On Wed, Sep 11, 2002 at 01:48:25AM -0400, Roland McGrath wrote:
> > PS: Running aafire on the client and scrolling up a couple of lines with
> >     LeftAlt + ArrowUp, while the top of aafire's output keeps running in
> >     the bottom half of the screen, is quite a neat effect if you are used to
> >     the jumpy Linux console which doesn't like output while being scrolled
> >     back.
> I prefer the docile behavior too.  But it should be a user option (as it is
> in xterm).  In fact, two options: jump down on new output, and jump down on
> typing.

Ok, I added the options --jump-down-on-output and --jump-down-on-input which
do exactly that.  I decided to make both options global:  The
--jump-down-on-output option is naturally global, but the
--jump-down-on-input option could just as well be per-input device.  OTOH,
nobody is helped with a zillion of possible configurations nobody is going
to need.  It's a small change to get per-input-device settings for this if
it ever becomes desirable.

I have not checked in my code yet as I decided that I have a bit more time
for some more changes, some of which require some small interface changes as
well, so I want to do them now rather than later.

I hope to get these things done before checking in:

* Driver specific option parsing.
* Multiple font support (so we can support sitm/ritm and some real bold
  attribute for use as faces in emacs).
* Screensaver interface and driver
* NumLock and CapsLock support in the simple keyboard driver
* ncursesw integration
* fixing an emacs display bug


* Copy & Paste (and mouse driver)
* Combining characters (I have an idea how to do this)

I will keep up to date tar balls on alpha.gnu.org, but not announce them
anymore here on this list.  Most of the above items are rather easy to
implement (except the last two), so I expect to make fast progress with
them.  At any time inbetween those tasks I might just check the code if I
decide that I need a break.

Things I leave for later, because they are rather big and/or isolated:

* xkb support
* svgatextmode support
* framebuffer driver
* configuration screen
* other drivers (gtk, vnc)


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

reply via email to

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