From: richard.banach@manchester.ac.uk (Richard Banach)
To: tim.visher@gmail.com, richard.banach@manchester.ac.uk
Cc: marioxcc.MT@yandex.com, help-gnu-emacs@gnu.org
Subject: Re: emacs -nw niggles
Date: Tue, 29 Aug 2017 14:36:13 +0100 [thread overview]
Message-ID: <20170829133613.9E0B8301033@cspc120.cs.man.ac.uk> (raw)
In-Reply-To: <CAHa53uwy8SRjL_NVNZ-ELQTQ_i=QrauOs+XOcvx2+MwqAN-XNQ@mail.gmail.com>
hi Tim,
| `emacs -nw` is subject to the TERM settings of the terminal it's running
| in. Depending on your distro that may be an 8 or 256 color variant. I'm
| suspicious based on your descriptions that your TERM setting may have
| changed recently.
ok yes ......... but it wasn't that recent ... i've only just got round
to trying to fix it
| The 256 color default them of emacs is much more subtle
| than the 8 color theme.
i'm sure ... but with imperfect eyesight 'crude and brutal' works
much better than 'subtle' for me :-)
| You can see what your TERM setting is by `echo $TERM` and you can see how
| many colors emacs thinks it can display by `M-x list-colors-display`.
echo $TERM ... straightforwardly gives 'xterm'
list-colors-display gives:
black #000000
red #cd0000
green #00cd00
yellow #cdcd00
blue #0000ee
magenta #cd00cd
cyan #00cdcd
white #e5e5e5
in effect, if i could change the 'cd's to 'ff's in the above (as picked
up by the keyword bindings for latex), i'd most likely be quite happy .....
is there a way of achieving that in emacs itself? ... other TERMs are
fine with the colours as is
| FWIW, some terminals allow you to change the TERM setting to something else
| if you'd prefer the 8 color variant.
thanks
richard.
next prev parent reply other threads:[~2017-08-29 13:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 16:42 emacs -nw niggles Richard Banach
2017-08-26 13:12 ` Mario Castelán Castro
2017-08-29 13:04 ` Richard Banach
2017-08-29 13:14 ` Tim Visher
2017-08-29 13:36 ` Richard Banach [this message]
2017-08-29 13:43 ` Tim Visher
2017-08-29 13:53 ` Richard Banach
2017-08-29 16:38 ` Mario Castelán Castro
2017-08-29 17:12 ` Richard Banach
2017-08-29 19:06 ` Mario Castelán Castro
2017-08-30 13:49 ` Richard Banach
2017-08-30 14:16 ` Mario Castelán Castro
2017-08-30 14:51 ` Richard Banach
2017-08-30 14:53 ` Mario Castelán Castro
2017-08-30 15:33 ` Tim Visher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170829133613.9E0B8301033@cspc120.cs.man.ac.uk \
--to=richard.banach@manchester.ac.uk \
--cc=help-gnu-emacs@gnu.org \
--cc=marioxcc.MT@yandex.com \
--cc=tim.visher@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).