Date: Sun, 9 Apr 2017 15:55:31 +0300 From: Andrey Chernov <ache@freebsd.org> To: Bruce Evans <brde@optusnet.com.au> Cc: Bruce Evans <bde@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r316642 - head/sys/dev/syscons Message-ID: <579d9011-a042-4f69-892a-703042706bd3@freebsd.org> In-Reply-To: <20170409195358.I2327@besplex.bde.org> References: <201704081000.v38A0dBU078784@repo.freebsd.org> <4a498d83-3b64-18ac-bb0f-890a0c2893fc@freebsd.org> <20170409150512.B1318@besplex.bde.org> <5d76f933-7d70-411f-9233-0f1e6b72023e@freebsd.org> <20170409195358.I2327@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09.04.2017 13:32, Bruce Evans wrote: > How do you initialize actual use of sc->cursor_char? It is only used > when SC_NO_FONT_LOADING is not defined. Configuring SC_PIXEL_MODE > forces SC_NO_FONT_LOADING to be undefined. Except to test sc->cursor_char, I use text console mode with loading national codepage font. I don't touch sc->cursor_char directly, I only use 'vidcontrol -M' to move range start to 0x03 since 0xd0-0xd3 and 0xd4 are valid characters in my codepage. Loading font and changing mousechar start are both through rc.conf variables: font8x14="cp866-8x14" font8x16="cp866b-8x16" font8x8="cp866-8x8" mousechar_start="3" > is almost always defined. Apparently the char cursor is turned off with > loadable fonts since it would mess up special fonts more than the default > font. But not as much as the mouse cursor. If you mean just cursor, I have it (even not block but underline cursor). It is not strictly char (i.e. text cursor), but emulation of it via loaded font change on the fly. Via rc.conf variable too: cursor="destructive"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?579d9011-a042-4f69-892a-703042706bd3>