unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: kj <socyl@987jk.com.invalid>
Subject: Re: TERM=xterm-256color but emacs=8color
Date: Tue, 4 Jan 2005 12:35:42 +0000 (UTC)	[thread overview]
Message-ID: <cre2iu$rne$1@reader1.panix.com> (raw)
In-Reply-To: crdne8$ohm$1@reader1.panix.com

In <crdne8$ohm$1@reader1.panix.com> kj <socyl@987jk.com.invalid> writes:

>In <mailman.10832.1104815808.27204.help-gnu-emacs@gnu.org> "Eli Zaretskii" <eliz@gnu.org> writes:

>>> From: kj <socyl@987jk.com.invalid>
>>> Date: Tue, 4 Jan 2005 01:30:31 +0000 (UTC)
>>> 
>>> Well, I just compiled emacs from the CVS codebase, but when I run
>>> *this* emacs -nw on an xterm that I *know* (thanks to vttest/dynamic.sh)
>>> supports more than 8 colors, *still* list-colors-display shows only
>>> 8 colors.

>>Does it work if you invoke Emacs like this:

>>  emacs -nw --color=256

>>?

>No.  I tried --color=NUM for NUM=0, 16, 88, and 256.  In every case
>list-colors-display showed only 8 colors.


SUCCESS!!!  THANKS FOR YOUR HELP!  The problem was a bad termcap
file.  I got a good one from my xterm's distribution, set TERM to
xterm-256color, and bingo!  list-colors-display now lists a huge
number of colors; I don't even need the --color=256 option on the
command line.

Now I have a new problem.  The Emacs installation that I get from
"make install" is MUCH larger than my ISP's measly disk quota will
allow.  My ISP already provides a full Emacs 21.3.1 installation
in /usr/local/share/emacs, so I was hoping to piggyback on that
installation and only use from my CVS compile the emacs-21.3.50
executable and whatever else it needs to support 256 colors.  But
naively copying the emacs-21.3.50 executable from /tmp/inst/bin to
my $HOME/bin did not work.  emacs-21.3.50 complains bitterly:

    Warning: arch-dependent data dir (/tmp/inst/libexec/emacs/21.3.50/i386-unknown-netbsdelf2.0/) does not exist.
    Warning: Lisp directory `/tmp/inst/share/emacs/21.3.50/site-lisp' does not exist.
    Warning: Lisp directory `/tmp/inst/share/emacs/site-lisp' does not exist.
    Warning: Lisp directory `/tmp/inst/share/emacs/21.3.50/leim' does not exist.
    Warning: Lisp directory `/tmp/inst/share/emacs/21.3.50/lisp' does not exist.


I gather from strings emacs-21.3.50|grep that the installation
directory is compiled into the Emacs executable.  So I'll probably
have to recompile Emacs with a different prefix in the configuration,
even though "make install" will be thwarted by the disk quota.

I'm scratching my head about how to get this to go...

kj



-- 
NOTE: In my address everything before the first period is backwards;
and the last period, and everything after it, should be discarded.

  reply	other threads:[~2005-01-04 12:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02 14:57 TERM=xterm-256color but emacs=8color kj
2005-01-02 15:11 ` David Hansen
2005-01-02 19:13 ` Peter Dyballa
2005-01-02 22:32   ` Eli Zaretskii
     [not found]   ` <mailman.10549.1104706035.27204.help-gnu-emacs@gnu.org>
2005-01-04  1:30     ` kj
2005-01-04  5:02       ` Eli Zaretskii
     [not found]       ` <mailman.10832.1104815808.27204.help-gnu-emacs@gnu.org>
2005-01-04  9:25         ` kj
2005-01-04 12:35           ` kj [this message]
2005-01-04 19:37             ` Peter Dyballa
2005-01-04 21:20             ` Eli Zaretskii
2005-01-04 11:06       ` Peter Dyballa
2005-01-04 21:13         ` Eli Zaretskii
2005-01-02 22:13 ` Eli Zaretskii

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='cre2iu$rne$1@reader1.panix.com' \
    --to=socyl@987jk.com.invalid \
    /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).