Re: SVGATextMode on 2.6.11

2005-03-22 Thread Alan Curry
Andries Brouwer writes the following: > >> "Alan Curry" <[EMAIL PROTECTED]> wrote: >>> An SVGATextMode >>> block cursor isn't affected by ^[c -- it truly *becomes* the default > >True - it is obtained by hardware reprogramming. But having lots of programs >touch the hardware is getting less

Re: SVGATextMode on 2.6.11

2005-03-22 Thread Andries Brouwer
> "Alan Curry" <[EMAIL PROTECTED]> wrote: >> >> With 2.6.11, I can no longer change the cursor with SVGATextMode. Previously, >> a block cursor could be selected by >> echo Cursor 0-31 >> /etc/TextConfig ; SVGATextMode >> and the cursor would be a block. On all consoles. Forever. >> >> To

Re: SVGATextMode on 2.6.11

2005-03-22 Thread Andries Brouwer
Alan Curry [EMAIL PROTECTED] wrote: With 2.6.11, I can no longer change the cursor with SVGATextMode. Previously, a block cursor could be selected by echo Cursor 0-31 /etc/TextConfig ; SVGATextMode and the cursor would be a block. On all consoles. Forever. To accomplish the same thing

Re: SVGATextMode on 2.6.11

2005-03-22 Thread Alan Curry
Andries Brouwer writes the following: Alan Curry [EMAIL PROTECTED] wrote: An SVGATextMode block cursor isn't affected by ^[c -- it truly *becomes* the default True - it is obtained by hardware reprogramming. But having lots of programs touch the hardware is getting less popular. Yes, I

Re: SVGATextMode on 2.6.11

2005-03-21 Thread Andrew Morton
"Alan Curry" <[EMAIL PROTECTED]> wrote: > > With 2.6.11, I can no longer change the cursor with SVGATextMode. Previously, > a block cursor could be selected by > echo Cursor 0-31 >> /etc/TextConfig ; SVGATextMode > and the cursor would be a block. On all consoles. Forever. > > To accomplish the

Re: SVGATextMode on 2.6.11

2005-03-21 Thread Andrew Morton
Alan Curry [EMAIL PROTECTED] wrote: With 2.6.11, I can no longer change the cursor with SVGATextMode. Previously, a block cursor could be selected by echo Cursor 0-31 /etc/TextConfig ; SVGATextMode and the cursor would be a block. On all consoles. Forever. To accomplish the same thing

Re: SVGATextMode on 2.6.11

2005-03-04 Thread Alan Curry
I wrote: > >Was SVGATextMode's cursor-setting ability removed as a result of an >intentional change, or might it get fixed? Or might CUR_DEFAULT become >tunable? Maybe another control sequence could make the current cursor >settings the default, like setterm -store does for foreground and

Re: SVGATextMode on 2.6.11

2005-03-04 Thread Alan Curry
I wrote: Was SVGATextMode's cursor-setting ability removed as a result of an intentional change, or might it get fixed? Or might CUR_DEFAULT become tunable? Maybe another control sequence could make the current cursor settings the default, like setterm -store does for foreground and background

SVGATextMode on 2.6.11

2005-03-02 Thread Alan Curry
With 2.6.11, I can no longer change the cursor with SVGATextMode. Previously, a block cursor could be selected by echo Cursor 0-31 >> /etc/TextConfig ; SVGATextMode and the cursor would be a block. On all consoles. Forever. To accomplish the same thing using the softcursor escape sequences, I

SVGATextMode on 2.6.11

2005-03-02 Thread Alan Curry
With 2.6.11, I can no longer change the cursor with SVGATextMode. Previously, a block cursor could be selected by echo Cursor 0-31 /etc/TextConfig ; SVGATextMode and the cursor would be a block. On all consoles. Forever. To accomplish the same thing using the softcursor escape sequences, I