Date: Thu, 1 Feb 2001 01:20:17 +0200 From: Peter Pentchev <roam@orbitel.bg> To: freebsd-hackers@FreeBSD.org Subject: Re: escape sequence for 'Ic' terminal capability Message-ID: <20010201012016.A9412@ringworld.oblivion.bg> In-Reply-To: <20010109100501.C2550@ringworld.oblivion.bg>; from roam@orbitel.bg on Tue, Jan 09, 2001 at 10:05:01AM %2B0200 References: <20010109100501.C2550@ringworld.oblivion.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 09, 2001 at 10:05:01AM +0200, Peter Pentchev wrote:
> Hi,
>
> I'm thinking of messing with the syscons ioctl handler to allow setting
> of color values - all EGA- and VGA-compatible video controllers allow this.
> The idea is to later define my termcap(5) entry to let ncurses deal with
> color setting.
>
> termcap(5) lists the 'cc' - 'can change color' and 'Ic' - 'initialize color'
> capabilities. Setting the boolean 'cc' is easy, 'Ic' however presents a bit
> of a problem to me - does anyone know what it is set to on any other terms
> so I can keep a bit of compatibility here, or do I just randomly pick an esc
> sequence, and lead on a happy existence until someone else defines this same
> esc sequence to do something else? :)
OK, since I started this thread, I got several suggestions, mainly
pointing me at the FBIO_{GET,SET}PALETTE console ioctl's. I still
need the 'Ic' capability to transfer the color information across
network connections (yes, both machines will be running fbsd with
identical kernel/userland local mods).
So my original question still stands: has anybody seen the 'Ic'
capability actually used in some OS's termcap, so I can borrow
the sequence with an eye on compatiblity, or has 'Ic' been just
a nice idea that nobody has bothered to implement?
G'luck,
Peter
--
This sentence every third, but it still comprehensible.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010201012016.A9412>