From: Martin Karlsson <qsvans@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs -nw, xterm and 256 colors [solved]
Date: Thu, 29 Mar 2007 20:54:22 +0200 [thread overview]
Message-ID: <86wt0zubhd.fsf@soeren.network.lan> (raw)
In-Reply-To: m2fy7ooxxj.fsf@sl392.st-edmunds.cam.ac.uk
Leo wrote:
> That looks awesome. What specifically did you do to get there?
First off, most of the following explanation is me guessing, not hard
facts.
Secondly, since you're on Linux, I'm guessing your system favours
terminfo over termcap. I'm using FreeBSD, which unfortunately seems to
rely more on (the older) termcap.
In short, my terminfo.db has a valid xterm-256color entry (which I
believe is ignored by many apps), and has termcap.db entries which map
all xterms with more tha 8 colours to an xterm TERM *with* 8 colours.
In other words, when i set my TERM to xterm-256color, xterm happily
obliges since it looks in terminfo. That only gives the actual xterm
access to all those nice colours though.
Some other apps (including emacs), [again this is on FreeBSD -- may or
may not apply to linuxen] use termcap, and conlude that my xterm is only
capable of displaying 8 colours.
Having said that, the full story (meager and potentially wildly
dangerous as it may be) can be found at:
<http://martink.freeshell.net/emacs/emacs-256xterm.txt>
Good luck,
--
Martin Karlsson
next prev parent reply other threads:[~2007-03-29 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 14:54 emacs -nw, xterm and 256 colors Martin Karlsson
2007-03-28 15:53 ` Leo
2007-03-29 12:22 ` emacs -nw, xterm and 256 colors [solved] Martin Karlsson
2007-03-29 13:01 ` Leo
2007-03-29 15:17 ` Martin Karlsson
2007-03-29 15:46 ` Leo
2007-03-29 18:54 ` Martin Karlsson [this message]
[not found] ` <mailman.1591.1175194608.7795.help-gnu-emacs@gnu.org>
2007-03-29 21:53 ` Ilya Zakharevich
2007-03-30 21:24 ` Martin Karlsson
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=86wt0zubhd.fsf@soeren.network.lan \
--to=qsvans@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).