All I want is white on dark background or vise versa.

Thanks
James

James <hslee911@yahoo.com> writes:
> All I want is white on dark background or vise versa.

Try ":syntax off".

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */

On Tuesday, February 15, 2022 at 12:30:56 PM UTC-8, Keith Thompson wrote:
> James writes:
> > All I want is white on dark background or vise versa.
> Try ":syntax off".
>
> --
> Keith Thompson (The_Other_Keith) Keith.S.T...@gmail.com
> Working, but not speaking, for Philips
> void Void(void) { Void(); } /* The recursive call of the void */

Thanks, it worked. Also added in ~/.vimrc

In comp.unix.shell, Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
> James <hslee911@yahoo.com> writes:
>> All I want is white on dark background or vise versa.
> Try ":syntax off".

That turns off syntax highlighting, but colors can still slip through
(I think search highlighting, for example).

I use ":set t_Co=0" to tell vim the terminal supports zero colors, then
it doesn't ever try to use them. If enabled, syntax highlighting falls
back to things like bold text.

Elijah
------
but usually disables syntax highlighting, too

In article <eli$2202151600@qaz.wtf>,
Eli the Bearded <*@eli.users.panix.com> wrote:
....
>I use ":set t_Co=0" to tell vim the terminal supports zero colors, then
>it doesn't ever try to use them. If enabled, syntax highlighting falls
>back to things like bold text.

That's really neat! I've long been frustrated by the fact that syntax
highlighting looks like junk on the default terminal setup on the RPi.

I really like syntax highlighting, so I don't want to turn it off, and I
usually use GVIM, wherein the colors are handled right and it is very
pretty, but in the terminal, it is junk.

I note, incidentally, that you can't put this in a modeline (it complains),
but you can do:

$ vim -c 'set t_Co=0' file

and it works nicely.

--
Modern Conservative: Someone who can take time out from flashing her
wedding ring around and bragging about her honeymoon to complain that a
fellow secretary who keeps a picture of her girlfriend on her desk is
"flauting her sexuality" and "forcing her lifestyle down our throats".

Eli the Bearded <*@eli.users.panix.com> writes:
> In comp.unix.shell, Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
>> James <hslee911@yahoo.com> writes:
>>> All I want is white on dark background or vise versa.
>> Try ":syntax off".
>
> That turns off syntax highlighting, but colors can still slip through
> (I think search highlighting, for example).
>
> I use ":set t_Co=0" to tell vim the terminal supports zero colors, then
> it doesn't ever try to use them. If enabled, syntax highlighting falls
> back to things like bold text.

":help termcap-options" for more information.

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */

Le 15/02/22 à 20:13, James a écrit :
> All I want is white on dark background or vise versa.
>
> Thanks
> James
>

I don't know if it's only me, but if I save the file as .txt, the syntax
highlighting is off.

--
Ottavio Caruso

On Tue, 15 Feb 2022 12:13:02 -0800 (PST)
James <hslee911@yahoo.com> wrote:
> All I want is white on dark background or vise versa.

For future reference , comp.editors is more appropriate for this kind
of question.

James <hslee911@yahoo.com> wrote:
> All I want is white on dark background or vise versa.

Just make vi (or any other program) believe that you are working in an
old monochrome terminal.

TERM=vt220 vi

On 12.03.2022 02:40, Javier wrote:
> James <hslee911@yahoo.com> wrote:
>> All I want is white on dark background or vise versa.
>
> Just make vi (or any other program) believe that you are working in an
> old monochrome terminal.
>
> TERM=vt220 vi

I recall from former times that a generic term (pun not intended) for
the terminal identifier was 'dumb' (TERM=dumb vi). I just tried and
noticed that it works but (e.g.) using the arrow keys for navigation
would not be possible any more (as opposed to using vt100 or similar),
so you'd have to use HJKL. - Are there such side effects for mimicking
any VT terminal? - If so, the syntax-deactivation would be preferable.

Janis

Janis Papanagnou <janis_papanagnou@hotmail.com> wrote:
> On 12.03.2022 02:40, Javier wrote:
>> James <hslee911@yahoo.com> wrote:
>>> All I want is white on dark background or vise versa.
>>
>> Just make vi (or any other program) believe that you are working in an
>> old monochrome terminal.
>>
>> TERM=vt220 vi
>
> I recall from former times that a generic term (pun not intended) for
> the terminal identifier was 'dumb' (TERM=dumb vi). I just tried and
> noticed that it works but (e.g.) using the arrow keys for navigation
> would not be possible any more (as opposed to using vt100 or similar),
> so you'd have to use HJKL. - Are there such side effects for mimicking
> any VT terminal? - If so, the syntax-deactivation would be preferable.

With TERM=vt220 all keys should be working. With something older
like 'TERM=vt100 vi' you would be missing 'Page Up/Page Down' keys.

That's why I used TERM=vt220 in my former message, as it is more modern
(from year 1990) and had more features than vt100 (like Page Up/Page Down).

On 2022-03-12, Janis Papanagnou <janis_papanagnou@hotmail.com> wrote:

>> TERM=vt220 vi
>
> I recall from former times that a generic term (pun not intended) for
> the terminal identifier was 'dumb' (TERM=dumb vi). I just tried and
> noticed that it works but (e.g.) using the arrow keys for navigation
> would not be possible any more (as opposed to using vt100 or similar),

Traditionally, a "dumb" terminal has the features of a teletype or
such:

$ TERM=dumb infocmp
# Reconstructed via infocmp from file: /usr/share/terminfo/d/dumb
dumb|80-column dumb tty,
am,
cols#80,
bel=^G, cr=^M, cud1=^J, ind=^J,

In particular, it does not support arbitrary cursor positioning.
vi(1) is not usable with it, although ex(1) is.

> so you'd have to use HJKL. - Are there such side effects for mimicking
> any VT terminal? - If so, the syntax-deactivation would be preferable.

It's not what you had in mind, but there were VT terminals before
the VT100. The control sequences of the VT52 are not compatible
with the VT100 et seq.

--
Christian "naddy" Weisgerber naddy@mips.inka.de

On 15/02/2022 20:13, James wrote:
> All I want is white on dark background or vise versa.
>
> Thanks
> James
>

Put 'syntax off' at the end of your .vimrc file.

--
Chris Elvidge
England

In article <t0klig$j7j$2@dont-email.me>,
Chris Elvidge <chris@mshome.net> wrote:
>On 15/02/2022 20:13, James wrote:
>> All I want is white on dark background or vise versa.
>>
>> Thanks
>> James
>>
>
>Put 'syntax off' at the end of your .vimrc file.

Or just turn the computer off. (I.e., turning syntax off is about as
stupid as turning the whole computer off).

Anyway, this question was recently raised and answered - in a slightly
different guise, but the same basic question - in one or the other of these
newsgroups - I think either this one (shell) or comp.editors. And the
answer, provided, I think, by Mr. Elijah, was to do:

set t_Co=0

This tells vim that your terminal has zero colors. You still get syntax
highlighting (which is key), but it is all done with shades of black,
white, and grey.

I find this useful - and have an alias of:

alias vi='vim -c "set t_Co=0"'

in my LXDE windows. Because for some reason, the combination of LXDE's
default color scheme (white on black) and VIM's color scheme for syntax
highlighting (particularly, for shell scripts) is horrid.

--
"If our country is going broke, let it be from feeding the poor and caring for
the elderly. And not from pampering the rich and fighting wars for them."

--Living Blue in a Red State--

On Sun, 13 Mar 2022 15:16:02 -0000 (UTC), Kenny McCormack wrote:
>
> In article <t0klig$j7j$2@dont-email.me>,
> Chris Elvidge <chris@mshome.net> wrote:
>>On 15/02/2022 20:13, James wrote:
>>> All I want is white on dark background or vise versa.
>>>
>>Put 'syntax off' at the end of your .vimrc file.
>
> Or just turn the computer off. (I.e., turning syntax off is about as
> stupid as turning the whole computer off).

With highlighting it looks bad on my greyscale CRT. ;-)

But highlighting also consumes CPU time. That was noticed on a fairly
large text file.

| 'redrawtime' exceeded, syntax highlighting disabled

It also take about 3 seconds to loads. Irritating that parts of the text
has syntax highlighting, the other not.

Solution is

set re=0

to disable the regex machine. With that the large page loads in a flash.

F'up2 comp.editors
--
Andreas

In message <t0l1ri$1j650$1@news.xmission.com> Kenny McCormack <gazelle@shell.xmission.com> wrote:
> In article <t0klig$j7j$2@dont-email.me>,
> Chris Elvidge <chris@mshome.net> wrote:
>>On 15/02/2022 20:13, James wrote:
>>> All I want is white on dark background or vise versa.
>>>
>>> Thanks
>>> James
>>>
>>
>>Put 'syntax off' at the end of your .vimrc file.

> Or just turn the computer off. (I.e., turning syntax off is about as
> stupid as turning the whole computer off).

> Anyway, this question was recently raised and answered - in a slightly
> different guise, but the same basic question - in one or the other of these
> newsgroups - I think either this one (shell) or comp.editors. And the
> answer, provided, I think, by Mr. Elijah, was to do:

> set t_Co=0

That will come in handy for those times where one particular color
(usually the dark blue) is unreadable my screen. I'd completely
forgotten about this setting but I did use it quite some time ago when I
had a greyscale 'page view' monitor.

--
Everybody knows the "secret sexy maid on the outside" trope.

Lewis <g.kreme@kreme.dont-email.me> writes:

> In message <t0l1ri$1j650$1@news.xmission.com> Kenny McCormack <gazelle@shell.xmission.com> wrote:
>> In article <t0klig$j7j$2@dont-email.me>,
>> Chris Elvidge <chris@mshome.net> wrote:
>>>On 15/02/2022 20:13, James wrote:
>>>> All I want is white on dark background or vise versa.
>>>>
>>>> Thanks
>>>> James
>>>>
>>>
>>>Put 'syntax off' at the end of your .vimrc file.
>
>> Or just turn the computer off. (I.e., turning syntax off is about as
>> stupid as turning the whole computer off).
>
>> Anyway, this question was recently raised and answered - in a slightly
>> different guise, but the same basic question - in one or the other of these
>> newsgroups - I think either this one (shell) or comp.editors. And the
>> answer, provided, I think, by Mr. Elijah, was to do:
>
>> set t_Co=0
>
> That will come in handy for those times where one particular color
> (usually the dark blue) is unreadable my screen. I'd completely
> forgotten about this setting but I did use it quite some time ago when I
> had a greyscale 'page view' monitor.

That dark blue is a hazard.
Depending on your terminal program you can get rid of it.
xterm and rxvt can be tuned with x-resources.
I use cornflowerblue instead.
Other terminals are pretty sure to have a way.
Just because the escape sequence sent to the terminal is asking for blue
doesn't mean the terminal has to display blue.

--
Dan Espen

In comp.unix.shell Dan Espen <dan1espen@gmail.com> wrote:
>
> That dark blue is a hazard.
> Depending on your terminal program you can get rid of it.
> xterm and rxvt can be tuned with x-resources.
> I use cornflowerblue instead.
> Other terminals are pretty sure to have a way.
> Just because the escape sequence sent to the terminal is asking for blue
> doesn't mean the terminal has to display blue.

I also get anoyed by the dark blue on black background. It's especially
common in the syntax highlighting in 'emacs -nw'.

Which is the X-resource for xterm that disables a specific color?
I never used that.

Javier <invalid@invalid.invalid> writes:

> In comp.unix.shell Dan Espen <dan1espen@gmail.com> wrote:
>>
>> That dark blue is a hazard.
>> Depending on your terminal program you can get rid of it.
>> xterm and rxvt can be tuned with x-resources.
>> I use cornflowerblue instead.
>> Other terminals are pretty sure to have a way.
>> Just because the escape sequence sent to the terminal is asking for blue
>> doesn't mean the terminal has to display blue.
>
> I also get anoyed by the dark blue on black background. It's especially
> common in the syntax highlighting in 'emacs -nw'.
>
> Which is the X-resource for xterm that disables a specific color?
> I never used that.

Try this:

XTerm*color0: Black
XTerm*color1: Red
XTerm*color2: Green
XTerm*color3: Yellow
XTerm*color4: cornflowerBlue
XTerm*color5: Magenta
XTerm*color6: Cyan
XTerm*color7: White
XTerm*color8: gray
XTerm*color9: pink
XTerm*color10: YellowGreen
XTerm*color11: orange
XTerm*color12: turquoise
XTerm*color13: wheat
XTerm*color14: lightblue
XTerm*color15: tan

Rxvt accepts the "XTerm" resources.

--
Dan Espen

In message <t0lpec$jd6$1@dont-email.me> Dan Espen <dan1espen@gmail.com> wrote:
> Lewis <g.kreme@kreme.dont-email.me> writes:

>> In message <t0l1ri$1j650$1@news.xmission.com> Kenny McCormack <gazelle@shell.xmission.com> wrote:
>>> In article <t0klig$j7j$2@dont-email.me>,
>>> Chris Elvidge <chris@mshome.net> wrote:
>>>>On 15/02/2022 20:13, James wrote:
>>>>> All I want is white on dark background or vise versa.
>>>>>
>>>>> Thanks
>>>>> James
>>>>>
>>>>
>>>>Put 'syntax off' at the end of your .vimrc file.
>>
>>> Or just turn the computer off. (I.e., turning syntax off is about as
>>> stupid as turning the whole computer off).
>>
>>> Anyway, this question was recently raised and answered - in a slightly
>>> different guise, but the same basic question - in one or the other of these
>>> newsgroups - I think either this one (shell) or comp.editors. And the
>>> answer, provided, I think, by Mr. Elijah, was to do:
>>
>>> set t_Co=0
>>
>> That will come in handy for those times where one particular color
>> (usually the dark blue) is unreadable my screen. I'd completely
>> forgotten about this setting but I did use it quite some time ago when I
>> had a greyscale 'page view' monitor.

> That dark blue is a hazard.
> Depending on your terminal program you can get rid of it.

Oh, on MY terminal it's not a problem, but I am often using other
people's computers when I am trying to fix them, and changing the colors
every time is just annoying.

Also, my terminal is iTerm2, and on others machines I am in the Mac's
default Terminal.app, so there I would have to remember how to change
the color and then change the color.

--
I'm from a predominately black family --Eddie Murphy