From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: TERM=xterm-256color but emacs=8color
Date: Tue, 4 Jan 2005 12:06:50 +0100 [thread overview]
Message-ID: <BBAE4604-5E40-11D9-83DB-000D932A32C4@Web.DE> (raw)
In-Reply-To: <crcrjn$f2i$1@reader1.panix.com>
Am 04.01.2005 um 02:30 schrieb kj:
> In <mailman.10549.1104706035.27204.help-gnu-emacs@gnu.org> "Eli
> Zaretskii" <eliz@gnu.org> writes:
>
> * Are there any invocation flags required to bring up emacs with
> 256-color support?
--color MODE color mode for character terminals;
MODE defaults to `auto', and can also
be `never', `auto', `always',
or a mode name like `ansi8'
>
> * Is there *anything else* that I need to do to get Emacs with
> 256-color support?
I don't know! And I either don't know whether --color works since I
can't test it. Have you tried to ask the authors of the Elisp code?
> P.S. It took an eternity to compile (make bookstrap) emacs. Is
> there a quicker way? All I need is:
>
> * 256-color support
> * support for programming modes (lisp, perl, c, etc.)
> * e-shell
> * mail mode and RMAIL
> * lisp interaction mode
I never compile GNU Emacs from CVS. Usually I invoke configure. There
you can say --without-x (or such) and then too every graphics support
will be left out. Best, of course, is to invoke './configure --help' to
see all option and to deliberately set off what you don't need.
Besides all: how do you think you could address the extra 248 colours?
In X11 (and in the carbonized versions) you're using the X11 names for
colours, for ansi8 mode too there are names as in list-colors-display
...
--
Greetings
Pete
“I hope to die before I *have* to use Microsoft Word.”
- Donald E. Knuth, 2001-10-02 in Tübingen.
--
Mit friedvollen Grüßen
Pete <]
o __o |__ o HPV, the real
___o /I -\<, |o \ -\),-% high speed!
___/\ /\___./ \___...O/ O____.....`-O-'-()--o_________________
next prev parent reply other threads:[~2005-01-04 11:06 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
2005-01-04 19:37 ` Peter Dyballa
2005-01-04 21:20 ` Eli Zaretskii
2005-01-04 11:06 ` Peter Dyballa [this message]
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=BBAE4604-5E40-11D9-83DB-000D932A32C4@Web.DE \
--to=peter_dyballa@web.de \
--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).