From: Knut Petersen <Knut_Petersen@t-online.de>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: 2 more fbcon rotation bugs
Date: Fri, 18 Nov 2005 16:23:22 +0100 [thread overview]
Message-ID: <437DF1EA.7010906@t-online.de> (raw)
Hi Antonino,
For rotation values of 1 and 3 in combination with unusual font heights
there are
serious cursor problems:
standard 8x16 and arial 22x24: ok
comic 16x26 and bitstream 16x30: broken as described below.
1: Load e.g. bitstream 16x30 font and switch to rotation 1.
2: At the bash prompt, type "asdf > qwer" without the quotation marks
and without
hitting enter.
3: Try to delete the letters q,w,e,r and reenter them. Everything works
fine.
4: Now place the cursor immediately behind the letter f and delete it.
Everything ok.
5. Hit the key f to reenter that letter .... now something breaks:
a: an f is inserted at the correct position
b: an f flashes for a short period at the place of the first space,
then it is overwritten
by the correct space character and the blinking cursor
c: the > at the right of the cursor is permanently overwritten with
a blank and a
frozen underline of the cursor, the line now reads asdf _ _ qwer.
Deleting and reinserting the other characters before the > gives similar
results, e.g.
for the letter s the result is "asdd > qwer", the first d switching from
s to d fast but
visible and with the blinking cursor, the 2nd d (that should be an f)
permanently
underlined.
No problems are visible if only one string of letters (even a long one)
is entered and
edited at the bash prompt.
Any idea where to start? Can you reproduce the odd behaviour? My first
idea was
to look into ccw_cursor() and cw_cursor(), but as there are no errors
for long strings
if they do not contain spaces, > or other signs of a special meaning to
bash, I suppose
that this is not the right/only place to start. My system is slow (Via
Eden cpu, 533Mhz),
could it be that the bug is invisible on faster machines? ...
cu,
Knut
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
next reply other threads:[~2005-11-18 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 15:23 Knut Petersen [this message]
2005-11-18 20:23 ` 2 more fbcon rotation bugs Antonino A. Daplas
2005-11-19 10:12 ` Knut Petersen
2005-11-19 10:48 ` Antonino A. Daplas
2005-11-19 11:35 ` Antonino A. Daplas
2005-11-20 3:48 ` Antonino A. Daplas
2005-11-20 9:03 ` Knut Petersen
2005-11-20 9:58 ` Geert Uytterhoeven
2005-11-20 22:04 ` Antonino A. Daplas
2005-11-22 6:34 ` Knut Petersen
2005-11-22 7:48 ` Antonino A. Daplas
2005-11-22 8:01 ` Knut Petersen
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=437DF1EA.7010906@t-online.de \
--to=knut_petersen@t-online.de \
--cc=adaplas@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.