From: Len Trigg <len@netvalue.net.nz>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Bug in 256 color terminal, colors > first 8 appear as white
Date: Mon, 07 Jul 2008 10:08:01 +1200 [thread overview]
Message-ID: <hbd4lqfyym.wl%len@netvalue.net.nz> (raw)
In-Reply-To: <hbfxqmg1e0.wl%len@netvalue.net.nz>
Len Trigg wrote:
>
> Dan Nicolaescu wrote:
> > Do you have the header files for termcap or terminfo or ncurses installed?
> >
> > What do you get if you do:
> >
> > grep TERM emacs/src/config.h
>
> After getting your message, the grep gave me:
>
> /* #undef HAVE_TERMCAP_H */
> #define HAVE_TERMIOS_H 1
> /* #undef HAVE_TERM_H */
>
> So I installed libtermcap-devel (I'm on centos 5.2), and now after
> doing:
>
> make maintainer-clean && ./configure --prefix=/home2/len/local && make bootstrap install
>
> the grep gives me:
>
> #define HAVE_TERMCAP_H 1
> #define HAVE_TERMIOS_H 1
> /* #undef HAVE_TERM_H */
>
> Which looks better. However, the newly built emacs still exhibits the
> same problem. Is there more I need?
Following up myself, I found and installed ncurses-devel, and now the grep gives:
#define HAVE_TERMCAP_H 1
#define HAVE_TERMIOS_H 1
#define HAVE_TERM_H 1
And now list-colors-display shows all the colors correctly. So, to
summarize, it seems that both ncurses and termcap headers are needed
for this to work (maybe terminfo could be substituted for termcap?).
Thanks for pointing me in the right direction.
Cheers,
Len.
next prev parent reply other threads:[~2008-07-06 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 1:02 Bug in 256 color terminal, colors > first 8 appear as white Len Trigg
2008-07-04 1:50 ` Dan Nicolaescu
2008-07-06 21:15 ` Len Trigg
2008-07-06 22:08 ` Len Trigg [this message]
2008-07-07 3:03 ` Dan Nicolaescu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=hbd4lqfyym.wl%len@netvalue.net.nz \
--to=len@netvalue.net.nz \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.