Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #236276 > unrolled thread

Font color selection in MATE terminal

Back to article view | Back to linux.debian.user

Contents

  Font color selection in MATE terminal Richard Owlett <rowlett@cloud85.net> - 2021-06-22 15:20 +0200
    Re: Font color selection in MATE terminal Richard Owlett <rowlett@cloud85.net> - 2021-06-22 15:30 +0200
    Re: Font color selection in MATE terminal IL Ka <kazakevichilya@gmail.com> - 2021-06-22 15:30 +0200
      Re: Font color selection in MATE terminal Greg Wooledge <greg@wooledge.org> - 2021-06-22 15:50 +0200
        Re: Font color selection in MATE terminal Curt <curty@free.fr> - 2021-06-22 16:30 +0200
        Re: Font color selection in MATE terminal IL Ka <kazakevichilya@gmail.com> - 2021-06-22 16:30 +0200
    Re: Font color selection in MATE terminal "Andrew M.A. Cater" <amacater@einval.com> - 2021-06-22 15:30 +0200
      Re: Font color selection in MATE terminal Richard Owlett <rowlett@cloud85.net> - 2021-06-22 15:40 +0200
        Re: Font color selection in MATE terminal David Wright <deblis@lionunicorn.co.uk> - 2021-06-22 21:20 +0200
    Re: Font color selection in MATE terminal Richard Owlett <rowlett@cloud85.net> - 2021-06-22 16:00 +0200
      Re: Font color selection in MATE terminal IL Ka <kazakevichilya@gmail.com> - 2021-06-22 16:40 +0200
    Re: Font color selection in MATE terminal Andrei POPESCU <andreimpopescu@gmail.com> - 2021-06-22 16:40 +0200
      Re: Font color selection in MATE terminal David Wright <deblis@lionunicorn.co.uk> - 2021-06-22 17:40 +0200
        Re: Font color selection in MATE terminal Bret Busby <bret@busby.net> - 2021-06-22 18:50 +0200
      Re: Font color selection in MATE terminal Siard <shiems@mailbox.org> - 2021-06-22 18:30 +0200
        Re: Font color selection in MATE terminal Richard Owlett <rowlett@cloud85.net> - 2021-06-23 11:40 +0200
          Re: Font color selection in MATE terminal Siard <shiems@mailbox.org> - 2021-06-23 13:40 +0200
          At least a partial solution - was [Re: Font color selection in MATE  terminal] Richard Owlett <rowlett@cloud85.net> - 2021-06-23 14:30 +0200
        Re: Font color selection in MATE terminal Marc Shapiro <marcnshap@gmail.com> - 2021-07-02 07:40 +0200
          Re: Font color selection in MATE terminal Siard <shiems@mailbox.org> - 2021-07-02 13:30 +0200
            Re: Font color selection in MATE terminal Richmond <richmond@criptext.com> - 2021-07-02 18:10 +0200
    Re: Font color selection in MATE terminal Richmond <dnomhcir@gmx.com> - 2021-06-22 18:20 +0200
      Re: Font color selection in MATE terminal Peter Ehlert <pb21a@sdi-baja.com> - 2021-06-22 18:40 +0200
        Re: Font color selection in MATE terminal Richmond <dnomhcir@gmx.com> - 2021-06-22 20:50 +0200
      Re: Font color selection in MATE terminal Bret Busby <bret@busby.net> - 2021-06-22 19:00 +0200
        Re: Font color selection in MATE terminal Greg Wooledge <greg@wooledge.org> - 2021-06-22 19:50 +0200
          Re: Font color selection in MATE terminal Bret Busby <bret@busby.net> - 2021-06-22 20:30 +0200
            Re: Font color selection in MATE terminal Greg Wooledge <greg@wooledge.org> - 2021-06-22 20:50 +0200
              Re: Font color selection in MATE terminal Bret Busby <bret@busby.net> - 2021-06-22 21:20 +0200
                Re: Font color selection in MATE terminal David Wright <deblis@lionunicorn.co.uk> - 2021-06-22 21:30 +0200
                Re: Font color selection in MATE terminal Greg Wooledge <greg@wooledge.org> - 2021-06-22 21:30 +0200
    RESOLVED: Font color selection in MATE terminal Richard Owlett <rowlett@cloud85.net> - 2021-06-24 13:10 +0200

Page 2 of 2 — ← Prev page 1 [2]

#236764

Siard <shiems@mailbox.org> writes:

> On Thu, 1 Jul 2021 22:37 -0700, Marc Shapiro wrote:
>> On 6/22/21 9:23 AM, Siard wrote:
>> > In the MATE Terminal settings (Edit > Profile Preferences),
>> > tab 'Colors', under 'Palette', set 'Built-in schemes' to 'Custom'
>> > and change every color in the color palette to black.
>> >
>> > Here is a screenshot:
>> > https://i.postimg.cc/2yv17y3Y/mateterminalcolors.png
>> 
>> Why select 'Custom'?
>> 
>> Richard needs black on white, so he should select 'Black on white'.
>> It works for me.  I have been using 'Custom', Yellow on Black, like
>> my first monitor many years ago.  But selecting 'Black on white'
>> gives exactly that.
>
> Yes, but it did not work for Richard, and as 'Custom' worked for me,
> I came with this solution.
> Later, it turned out that it was caused by a glitch in MATE Terminal
> 1.16.3, used in Debian 9.  Later versions worked fine.
> So 'Black on white' is indeed the most obvious way.

Strangely, I am using MATE terminal 1.20 and now it is not working. I
have a profile called Black and White. I change the colour profile
preferences to the black and white scheme, but when I launch emacs -nw,
it displays blue underlined text in places. And when I go back and look
at the colour preferences in MATE it has gone back to custom.

[toc] | [prev] | [next] | [standalone]

#236309

Richard Owlett wrote:
> I have vision problems.
> I *MUST* have black on white text in all cases.
> The program I'm running gives out colored text.
> The MATE Help screen is NOT helpful.
> Help please.
>
>
On the menu bar of mate-terminal, select Edit -> Profile Preferences ->
Colours

Uncheck the box that says 'Use colours from system theme'. Select Built
In Scheme Black on White from the drop down list.

[toc] | [prev] | [next] | [standalone]

#236311

On 6/22/21 9:17 AM, Richmond wrote:
> Richard Owlett wrote:
>> I have vision problems.
>> I *MUST* have black on white text in all cases.
>> The program I'm running gives out colored text.
>> The MATE Help screen is NOT helpful.
>> Help please.
>>
>>
> On the menu bar of mate-terminal, select Edit -> Profile Preferences ->
> Colours
>
> Uncheck the box that says 'Use colours from system theme'. Select Built
> In Scheme Black on White from the drop down list.

The controls are there, but not _all_ of the Text is black.

I tested in Bullseye and Buster.

Richard Owlett perhaps you should file a bug report

>
>
>

[toc] | [prev] | [next] | [standalone]

#236320

Peter Ehlert wrote:
>
> On 6/22/21 9:17 AM, Richmond wrote:
>> Richard Owlett wrote:
>>> I have vision problems.
>>> I *MUST* have black on white text in all cases.
>>> The program I'm running gives out colored text.
>>> The MATE Help screen is NOT helpful.
>>> Help please.
>>>
>>>
>> On the menu bar of mate-terminal, select Edit -> Profile Preferences ->
>> Colours
>>
>> Uncheck the box that says 'Use colours from system theme'. Select Built
>> In Scheme Black on White from the drop down list.
>
> The controls are there, but not _all_ of the Text is black.
>
> I tested in Bullseye and Buster.
>
> Richard Owlett perhaps you should file a bug report
>
Ok but I don't think it is a bug. The preferences dialogue has a note
saying that all the colours the custom colour palette are available to
terminal applications. So I think amending the colour palette as Siard
says might do it.

<20210622182358.77011dfdebeacdacee2c4e80@mailbox.org>


>>
>>
>>
>

[toc] | [prev] | [next] | [standalone]

#236313

On 23/6/21 12:17 am, Richmond wrote:
> Richard Owlett wrote:
>> I have vision problems.
>> I *MUST* have black on white text in all cases.
>> The program I'm running gives out colored text.
>> The MATE Help screen is NOT helpful.
>> Help please.
>>
>>
> On the menu bar of mate-terminal, select Edit -> Profile Preferences ->
> Colours
> 
> Uncheck the box that says 'Use colours from system theme'. Select Built
> In Scheme Black on White from the drop down list.
> 
> 

Except, that does not stop colours from being displayed; for example, 
warnings are displayed in yellow text (on white background).

And, that also applies, if provision for coloured text is commented out, 
in the .bashrc file.

-- 
Bret Busby
Armadale
West Australia
(UTC+0800)
..............

[toc] | [prev] | [next] | [standalone]

#236314

On Wed, Jun 23, 2021 at 12:27:17AM +0800, Bret Busby wrote:
> And, that also applies, if provision for coloured text is commented out, in
> the .bashrc file.

There's nothing in .bashrc which controls the terminal's interpretation
of color escape sequences.  Or in bash, anywhere.

It's entirely between the terminal, and the application which generates
the color sequences.  The shell is not involved.

The closest the shell comes to being involved is if you try to trick the
application into thinking it's on a different kind of terminal, by
changing the TERM variable.  This rarely works out well, except in
very specific circumstances -- the most notable being "I'm ssh-ing to
a system that doesn't know about my terminal type".

As I've already tested today, it sure as hell doesn't work for apt(8).

[toc] | [prev] | [next] | [standalone]

#236316

On 23/6/21 1:42 am, Greg Wooledge wrote:
> On Wed, Jun 23, 2021 at 12:27:17AM +0800, Bret Busby wrote:
>> And, that also applies, if provision for coloured text is commented out, in
>> the .bashrc file.
> 
> There's nothing in .bashrc which controls the terminal's interpretation
> of color escape sequences.  Or in bash, anywhere.
> 
> It's entirely between the terminal, and the application which generates
> the color sequences.  The shell is not involved.
> 
> The closest the shell comes to being involved is if you try to trick the
> application into thinking it's on a different kind of terminal, by
> changing the TERM variable.  This rarely works out well, except in
> very specific circumstances -- the most notable being "I'm ssh-ing to
> a system that doesn't know about my terminal type".
> 
> As I've already tested today, it sure as hell doesn't work for apt(8).
> 

Excerpt from .bashrc file:

"

# set a fancy prompt (non-color, unless we know we "want" color)
# case "$TERM" in
#    xterm-color|*-256color) color_prompt=yes;;
# esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

# if [ -n "$force_color_prompt" ]; then
#    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
#	# We have color support; assume it's compliant with Ecma-48
#	# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
#	# a case would tend to support setf rather than setaf.)
#	color_prompt=yes
  #   else
  # next line commented out by me to prevent colouring of prompt
  #	color_prompt=
#    fi
# fi

# if [ "$color_prompt" = yes ]; then
   #  PS1='[\D{} \t] 
${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ 
'
#   PS1="\d \t \u@\h:\w$"
# else
    PS1='[\D{} \t] ${debian_chroot:+($debian_chroot)} `date `\u@\h:\w\$ '
# PS1="\d \t \u@\h:\w$"
# fi
# unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
#    PS1="[\D{} \t] \[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: 
`date `\w\a\]$PS1"
PS1="\d \t \u@\h:\w$"
     ;;
*)
     ;;
esac

# enable color support of ls and also add handy aliases
# if [ -x /usr/bin/dircolors ]; then
#     test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || 
eval "$(dircolors -b)"
#     alias ls='ls --color=auto'
#     #alias dir='dir --color=auto'
     #alias vdir='vdir --color=auto'

#    alias grep='grep --color=auto'
  #   alias fgrep='fgrep --color=auto'
#    alias egrep='egrep --color=auto'
# fi

# colored GCC warnings and errors
#export 
GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
# alias ll='ls -alF'
# alias la='ls -A'
# alias l='ls -CF'
"

-- 
Bret Busby
Armadale
West Australia
(UTC+0800)
..............

[toc] | [prev] | [next] | [standalone]

#236318

On Wed, Jun 23, 2021 at 02:27:04AM +0800, Bret Busby wrote:
> On 23/6/21 1:42 am, Greg Wooledge wrote:
> > There's nothing in .bashrc which controls the terminal's interpretation
> > of color escape sequences.  Or in bash, anywhere.

> Excerpt from .bashrc file:
> 
> "
> 
> # set a fancy prompt (non-color, unless we know we "want" color)
> # case "$TERM" in
> #    xterm-color|*-256color) color_prompt=yes;;
> # esac
> 
> # uncomment for a colored prompt, if the terminal has the capability; turned
> # off by default to not distract the user: the focus in a terminal window
> # should be on the output of commands, not on the prompt
> #force_color_prompt=yes

All of that code is just for setting the shell's prompt.  It has nothing
to do with how the terminal interprets color codes.

[toc] | [prev] | [next] | [standalone]

#236324

On 23/6/21 2:39 am, Greg Wooledge wrote:
> On Wed, Jun 23, 2021 at 02:27:04AM +0800, Bret Busby wrote:
>> On 23/6/21 1:42 am, Greg Wooledge wrote:
>>> There's nothing in .bashrc which controls the terminal's interpretation
>>> of color escape sequences.  Or in bash, anywhere.
> 
>> Excerpt from .bashrc file:
>>
>> "
>>
>> # set a fancy prompt (non-color, unless we know we "want" color)
>> # case "$TERM" in
>> #    xterm-color|*-256color) color_prompt=yes;;
>> # esac
>>
>> # uncomment for a colored prompt, if the terminal has the capability; turned
>> # off by default to not distract the user: the focus in a terminal window
>> # should be on the output of commands, not on the prompt
>> #force_color_prompt=yes
> 
> All of that code is just for setting the shell's prompt.  It has nothing
> to do with how the terminal interprets color codes.
> 

Funnily enough, given what you contend, before I commented out the 
colouring in stuff, when running ls -lh, directory names were displayed 
in blue text, and, after I commented out the colouring in stuff, running 
ls -lh, the output was all displayed in black text.

-- 
Bret Busby
Armadale
West Australia
(UTC+0800)
..............

[toc] | [prev] | [next] | [standalone]

#236325

On Wed 23 Jun 2021 at 03:13:00 (+0800), Bret Busby wrote:
> On 23/6/21 2:39 am, Greg Wooledge wrote:
> > On Wed, Jun 23, 2021 at 02:27:04AM +0800, Bret Busby wrote:
> > > On 23/6/21 1:42 am, Greg Wooledge wrote:
> > > > There's nothing in .bashrc which controls the terminal's interpretation
> > > > of color escape sequences.  Or in bash, anywhere.
> > 
> > > Excerpt from .bashrc file:
> > > 
> > > "
> > > 
> > > # set a fancy prompt (non-color, unless we know we "want" color)
> > > # case "$TERM" in
> > > #    xterm-color|*-256color) color_prompt=yes;;
> > > # esac
> > > 
> > > # uncomment for a colored prompt, if the terminal has the capability; turned
> > > # off by default to not distract the user: the focus in a terminal window
> > > # should be on the output of commands, not on the prompt
> > > #force_color_prompt=yes
> > 
> > All of that code is just for setting the shell's prompt.  It has nothing
> > to do with how the terminal interprets color codes.
> > 
> 
> Funnily enough, given what you contend, before I commented out the
> colouring in stuff, when running ls -lh, directory names were
> displayed in blue text, and, after I commented out the colouring in
> stuff, running ls -lh, the output was all displayed in black text.

Your "colouring in stuff" included dircolors.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#236326

On Wed, Jun 23, 2021 at 03:13:00AM +0800, Bret Busby wrote:
> Funnily enough, given what you contend, before I commented out the colouring
> in stuff, when running ls -lh, directory names were displayed in blue text,
> and, after I commented out the colouring in stuff, running ls -lh, the
> output was all displayed in black text.

OK, I made a slightly oversimplified statement.

MOST of the code in that excerpt goes into setting the shell's prompt.
There are also some aliases at the end, one of those being an alias
for ls, setting it up to use --color=auto.

So, the code that you posted affects two things:

1) Bash's shell prompt, which may or may not include color escape
   sequences.

2) Various aliases that change the default behavior of some commands
   (by adding options to what you type), including ls, which may cause
   ls to emit color escape sequences.

In all cases, the behavior of the terminal in response to these color
escape sequences is defined by the terminal itself, and may or may not
be user-configurable.

Nothing in .bashrc affects the terminal's behavior.  Only the terminal's
configuration affects that.

.bashrc controls the behavior of bash, not of the terminal.

[toc] | [prev] | [next] | [standalone]

#236400 — RESOLVED: Font color selection in MATE terminal

On 06/22/2021 08:14 AM, Richard Owlett wrote:
> I have vision problems.
> I *MUST* have black on white text in all cases.
> The program I'm running gives out colored text.
> The MATE Help screen is NOT helpful.
> Help please.
> 

There is a bug in MATE Terminal 1.16.3 [used in Debian 9] which prevents 
setting color preferences.

It is apparently resolve in MATE Terminal 1.20.2 [used in Debian 10].
I will not pursue further.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web