Re: console color

[lists]

> OK, thanks. After some searching based on this info and some messing 
> around, it looks like 'export TERM=ansi' and setting t_Co=8 will get me 
> limited colors in vim without screwing anything up.

Further to the excellent write-up by miod@ simply put if you're on x86
PC console any of these enables colors:

$ export TERM=wsvt25
$ export TERM=pccon

To confirm:

$ echo $TERM ; tput colors
$ tmux

These are defined in /etc/termcap

Hint: in the file search for (open|net)bsd|colou?r and Co#8|Co#256 for a
broader range of TERM capabilities.

You can also reference for an understanding what do the definitions in
/etc/termcap mean

$ man 5 terminfo
$ man 5 termcap

If you get sick of console colors and your eyes start hurting from dark
blue fg on black bg and other high-low contrast issue just set it back
to vt220:

$ export TERM=vt220

Or even better, use xterm. In X you can use

$ export TERM=xterm-256color
$ export TERM=screen-256color # slant instead of reverse highlight
$ export TERM=tmux-256color

You could also set TERM in .profile testing whether you're on the PC
console or in X, and whether you're running an interactive shell and/or
a tmux session.

Re: console color

[Karel Gardas]

For local console I've googled and TERM=wsvt25 brings colors to emacs
and vim for me on amd64.

On Mon, Sep 21, 2015 at 8:35 PM, Quartz  wrote:
> Can someone give be a brief rundown on how OpenBSD handles color on console?
> Commands like "echo -e '\033[32mfoo\033[0m'" produces dark green text as
> expected, but "echo -e '\033[92mfoo\033[0m'" comes out white instead of
> light green, and I can't seem to get vim to do syntax coloring at all (I've
> copied over configs that work on other machines, both t_Co=16 and t_Co=8,
> but everything always displays plain white). $TERM is the standard vt220. Am
> I doing something wrong, or does local console just have very limited color
> support?

Re: console color

[Miod Vallat]

> For local console I've googled and TERM=wsvt25 brings colors to emacs
> and vim for me on amd64.

wsvt25 (and wsvt43 and wsvt50) only are 8-color terminals, and that's
the best the kernels's console emulation code will provide; and this is
not going to change anytime soon. If you want 16 or 256 colors, run X.

Re: console color

[Miod Vallat]

> Can someone give be a brief rundown on how OpenBSD handles color on console?

It depends upon the terminal emulation being used. OpenBSD provides both
a `sun' terminal emulation, which is the default on sparc and sparc64
(use either TERM=sun for faithful behavioul or TERM=rcons-color for the
colour extensions), and a `vt220' terminal emulation, which is a subset
of the VT220 command set, with some xterm control sequences recognized
(use either TERM=vt220 or one of the wsvtXX matching your number of
rows).

The SGR (ESC [ * m) sequences recognized by the vt220 emulation are 0
(reset), 1 (bold), 4 (underline), 5 (blink), 7 (reverse video), 30-37
(select fg color), and 40-47 (select bg color) [in fact, a few VT300
sequences are also recognized but they don't matter here]. There is no
support for more than 8 color code using 90-97 and 100-107.

Also, keep in mind that, depending upon the actual video hardware being
used, the hardware may not be able to output what the escape sequences
are requesting. Not all hardware supports blinking or underline, for
example.

Re: console color

[Martin Brandenburg]

On Mon, 21 Sep 2015, Quartz wrote:

Can someone give be a brief rundown on how OpenBSD handles color on console? 
Commands like "echo -e '\033[32mfoo\033[0m'" produces dark green text as 
expected, but "echo -e '\033[92mfoo\033[0m'" comes out white instead of light 
green, and I can't seem to get vim to do syntax coloring at all (I've copied 
over configs that work on other machines, both t_Co=16 and t_Co=8, but 
everything always displays plain white). $TERM is the standard vt220. Am I 
doing something wrong, or does local console just have very limited color 
support?






The DEC VT220 terminal did not support color. That's why color works when 
you echo control codes and not through vim. Vim reads $TERM and decides 
not to use color.


Set $TERM up to something that supports color if you want color.

-- Martin

console color

[Quartz]

Can someone give be a brief rundown on how OpenBSD handles color on 
console? Commands like "echo -e '\033[32mfoo\033[0m'" produces dark 
green text as expected, but "echo -e '\033[92mfoo\033[0m'" comes out 
white instead of light green, and I can't seem to get vim to do syntax 
coloring at all (I've copied over configs that work on other machines, 
both t_Co=16 and t_Co=8, but everything always displays plain white). 
$TERM is the standard vt220. Am I doing something wrong, or does local 
console just have very limited color support?

Re: console color

[Quartz]

OK, thanks. After some searching based on this info and some messing 
around, it looks like 'export TERM=ansi' and setting t_Co=8 will get me 
limited colors in vim without screwing anything up.

Re: Alpha onboard PCI VGA console color issue.

[Matthieu Herrb]

On 7/25/07, Sean Kennedy [EMAIL PROTECTED] wrote:
 Hello 'alpha' / 'misc'

 Alpha console color question.

 I got a DS20E 833 uniprocessor Alpha with onboard PCI VGA
 ( vga0 at pci0 dev 7 function 0 3D Labs Oxygen GVX1 rev 0x01 )

 Running 4.1-GENERIC and have seen this since oBSD 3.8 when I began running
 oBSD on the unit.
 (nearly 2 years ago, wow!)

 OK my question is:

 Is there any one else running OpenBSD on an alpha in VGA console mode with
 wscons,
 and have when in multi-user mode, the console running with a blue
 background?
 The Blue background is present in all wscons displays.

 From MacPPC, and i386, Kernel Messages show up with Blue Background
 highlighting, and the background is black with nominal grey test.
 But on alpha, the background is always Blue, and may be triggered to black
 when running some utilities like vi.

 However even with the black background, the blue returns. and other
 highlights (bold text) do not appear.

 I would like to know in what direction I can look for the background color
 settings when wscons sets up the displays. There may be an update for the
 color palette that can be tested.

 Any pointers would help.


This is a known bug in wscons on alpha with VGA cards that has not
been identified yet.

Alpha onboard PCI VGA console color issue.

[Sean Kennedy]

Hello 'alpha' / 'misc'

Alpha console color question.

I got a DS20E 833 uniprocessor Alpha with onboard PCI VGA
( vga0 at pci0 dev 7 function 0 3D Labs Oxygen GVX1 rev 0x01 )

Running 4.1-GENERIC and have seen this since oBSD 3.8 when I began running 
oBSD on the unit.

(nearly 2 years ago, wow!)

OK my question is:

Is there any one else running OpenBSD on an alpha in VGA console mode with 
wscons,
and have when in multi-user mode, the console running with a blue 
background?

The Blue background is present in all wscons displays.

From MacPPC, and i386, Kernel Messages show up with Blue Background 

highlighting, and the background is black with nominal grey test.
But on alpha, the background is always Blue, and may be triggered to black 
when running some utilities like vi.


However even with the black background, the blue returns. and other 
highlights (bold text) do not appear.


I would like to know in what direction I can look for the background color 
settings when wscons sets up the displays. There may be an update for the 
color palette that can be tested.


Any pointers would help.

-sean

_
Get More out of Messenger - Get a Windows Live Space 
http://spaces.live.com/?mkt=en-ca