Date: Thu, 27 Jun 1996 08:36:53 +0200 (MET DST) From: sos@FreeBSD.ORG To: ache@nagual.ru (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Cc: sos@FreeBSD.ORG, andreas@klemm.gtn.com, current@FreeBSD.ORG Subject: Re: Syscons 8bit chars mouse paste fix Message-ID: <199606270636.IAA04861@ra.dkuug.dk> In-Reply-To: <199606262332.DAA00284@nagual.ru> from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Jun 27, 96 03:32:22 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= who wrote:
>
> > Any other gripes at the moment ??
>
> Yes, it start to paste 8bit chars, but it pust ANOTHER 8bit chars!
> The reason is simple: screen map not counted for C&P operation.
So, your patch didn't work proberly ?? :) :)
Ok, I'll put in the scrmap call :)
> Destructive cursor works now, but I notice that characters
> AA, B6, B7, BA becomes broken: they contains moving cursor image.
> They are frame pseudo-graphics in KOI8-R, many programs
> use them for frames (as my editor f.e.), effect is very strange.
Yes this is an artifact of how the mousepointer works, its the
chars D0-D3 actually, what you see must be because of your
scrmap. There is no fix for this, other than changeing the
involved chrs, just tomove the problem to another place. I chose
D0-D3 as they seemed to conflict the least in the charsets
that I use. Also the chars must be in the range that gets
bit 7 copied into bit 8 on 9 bit wide resolutions, which further
limits the available range.
> X incompatibility and rc incompatibility still exists.
Whats the griefs with X if both use /dev/cuaa? ??
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
So much code to hack -- so little time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606270636.IAA04861>