From: richard.banach@manchester.ac.uk (Richard Banach)
To: marioxcc.MT@yandex.com, help-gnu-emacs@gnu.org
Subject: Re: emacs -nw niggles
Date: Tue, 29 Aug 2017 14:04:09 +0100 [thread overview]
Message-ID: <20170829130409.D1106301033@cspc120.cs.man.ac.uk> (raw)
In-Reply-To: <1eee8652-c5e5-6b4a-b0a8-197ac24dfee7@yandex.com>
hi Mario,
thanks for the reply
| On 25/08/17 11:42, Richard Banach wrote:
| > * in tex mode, if I type $\it identifiername$ it doesn't recognise
| > the second $ as closing the scope of \it ... and wants to underline
| > everything that follows ... i haven't found how to turn this off
|
| Based on your description, this seems like a bug. I recommend opening a
| bug report.
ok ... i just mailed it in to bug-gnu-emacs@gnu.org ... hope that
will do the trick
| > * in the old days, it used the 'angry primary colors' color scheme, which
| > was great for someone with poor sight like me, ... nowadays pale pastel
| > schemes are the default ... how can I get 'angry primary colors' back?
|
| Try M-x "customize-themes"
i tried playing with that
a) a couple of themes i tried looked pretty pale to me
b) the customization only took effect in emacs running in its own
window ... in emacs -nw started in an xterm, the colours are
different (for the same latex file), the customizations have no effect,
and the keyword colour mapping (for latex keywords) is coming from some
other place, which i'd like to be able to edit if possible
| I have never seen "pale pastel" colors by default. What version of Emacs
| do you use?
it says
GNU Emacs 24.3.1 (x86_64-redhat-linux-gnu, GTK+ Version 3.14.13)
of 2017-03-03 on c1bm.rdu2.centos.org
thanks once more
richard.
next prev parent reply other threads:[~2017-08-29 13:04 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 [this message]
2017-08-29 13:14 ` Tim Visher
2017-08-29 13:36 ` Richard Banach
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=20170829130409.D1106301033@cspc120.cs.man.ac.uk \
--to=richard.banach@manchester.ac.uk \
--cc=help-gnu-emacs@gnu.org \
--cc=marioxcc.MT@yandex.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).