Re: setedit and elinks

[<wi...@po...>]

U=BFytkownik Salvador Eduardo Tropea <sal...@in...> napisa=B3:
>On 26/08/06 13:11, Witold Filipczyk wrote:
>
>>On Wed, Aug 23, 2006 at 01:37:52PM -0300, Salvador Eduardo Tropea wro=
te:
>> =20
>>
>>>On 19/08/06 22:38, Rohan Carly wrote:
>>>
>>>   =20
>>>
>>>>Witold Filipczyk wrote:
>>>>
>>>>
>>>>     =20
>>>>
>>>>>Another bug is a tvision bug. I use ATI framebuffer and
>>>>>cursor leaves trace. It's annoying.
>>>>> =20
>>>>>
>>>>>       =20
>>>>>
>>>>I also had that problem using framebuffer, not sure if it was the A=
TI=20
>>>>one or not. From memory (it was a while ago) I found that if I dele=
ted=20
>>>>/dev/vcs* (or maybe I just changed the permissions on those files- =
try=20
>>>>removing write access, or maybe read access) then the problem went =
away.
>>>>
>>>>
>>>>
>>>>     =20
>>>>
>>>The UseVCS=3D0 solution is more elegant for such a problem.
>>>   =20
>>>
>>I'm afraid that bytes 2 and 3 in /dev/vcsa? are read only properties =
for
>>framebuffers.
>> =20
>>
>
>Nope, they work (the cursor is moved), so they aren't read only.
>
>>This patch fixes the trace on the framebuffer
>> =20
>>
>
>
>That's a workaround and degradates the speed for non-framebuffer cases=
=20
>(or well implemented frame buffers).
>Do you know how to detect if the console is using framebuffer?

open("/dev/fb0", ...) ?
>
>This patch isn't a good solution, but I could add an option to enable=20
>such a workaround.

The option will be good. When UseVCS=3D1 and SetCursorPosOld=3D1
use SetCursorPos.

--=20
Witek