From: Dan Nicolaescu <dann@ics.uci.edu>
To: "Eric Johnson" <darrel.eric.johnson@gmail.com>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: font highlighting in emacs 22.1.1, os x build
Date: Fri, 13 Jul 2007 16:38:36 -0700 [thread overview]
Message-ID: <200707132338.l6DNcaQ9011782@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <4a8127b0707130647kcdb2274xd7e3cc576174265c@mail.gmail.com> (Eric Johnson's message of "Fri\, 13 Jul 2007 08\:47\:40 -0500")
"Eric Johnson" <darrel.eric.johnson@gmail.com> writes:
> I built emacs 22.1.1 on OS X (ppc). I was excited to hear that I would
> be able to run in both "aqua" mode and in console mode. However, font
> highlighting is not consistent between the two. In particular, the
> "aqua" mode seems to behave correctly (as per my experience with emacs
> 21.x), but console mode does not. It is sufficient to create a file
> named test.c, containing the following contents:
>
> /* this is a test */
>
> In the "aqua" version, all of the text within the comment will be
> colored to the appropriate comment color. However, in the console
> version, only the /* and */ are colored to the comment color; the
> remaining text is white.
>
> I am excited to use the latest version of emacs; however, I mainly use
> emacs from within the terminal. Consequently, I hope that a fix for
> this problem is possible, as otherwise I will continue to use version
> 21.x.
This only happens if your terminal supports only 8 colors.
Ideally, if you had a terminal that supported 256 colors then the
syntax coloring difference for emacs running in a terminal and in
windowing mode is almost indistinguishable.
I am not sure about your platform, but for GNU/Linux most recent
terminals support 256 colors, you'd just need to set TERM to
xterm-256color.
prev parent reply other threads:[~2007-07-13 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 13:47 font highlighting in emacs 22.1.1, os x build Eric Johnson
2007-07-13 23:09 ` Richard Stallman
2007-07-13 23:38 ` Dan Nicolaescu [this message]
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=200707132338.l6DNcaQ9011782@oogie-boogie.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=bug-gnu-emacs@gnu.org \
--cc=darrel.eric.johnson@gmail.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.
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.