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
> "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
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
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
"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
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
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
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
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
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
10 matches
Mail list logo