linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: James Simmons <jsimmons@infradead.org>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	geert@linux-m68k.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Cursor problems still in test9
Date: Thu, 30 Oct 2003 10:09:34 +0100	[thread overview]
Message-ID: <20031030090934.GC295@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0310300436440.28721-100000@phoenix.infradead.org>

Hi!

> > [And they get worse in fbcon-test patches I tried].
> > 
> > Try this on 2.4 (with vesafb).
> > 
> > echo -e "\33[10;5000]\33[11;50]\33[?18;0;136c\33[?102m"
> > 
> > ...then try it on 2.6, type foo in bash then delete it using
> > backspace; ghost cursors stay there. Run emacs and quit it (it sets
> > cursor to very visible). Boom, special cursor settings are gone.
> 
> I experimented with the above. I tried it out on vgacon, fbcon 2.4.X and 
> fbcon 2.6.X. All give different results. What are suppose to see? 

Well, we certainly do not want to see artifacts leaved behind cursor,
which is what 2.6 currently does. (Type something in bash, backspace
over it).

Making it behave like it does now with 2.6, but with cursor properly
deleted after after backspace, it would be okay.

[It should behave the same way on 2.4 vgacon and fbcon... with
possible difference that "bright background" might cause characters to
blink on vgacon. That depends on vga card setting and is not really
important.]

> > And now, use gpm on text console to select some text. Hold down left
> > button, move mouse a bit. Sometimes cursor gets corrupted and stays
> > there.
> 
> Will try.

Were you able to reproduce it?
								Pavel

-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

  reply	other threads:[~2003-10-30  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28  9:49 Cursor problems still in test9 Pavel Machek
2003-10-30  4:41 ` James Simmons
2003-10-30  9:09   ` Pavel Machek [this message]
2003-10-30 19:46     ` Nigel Cunningham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031030090934.GC295@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=geert@linux-m68k.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).