From: Eli Zaretskii <eliz@gnu.org>
To: Rob Riepel <riepel@networking.stanford.edu>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: incomplete comment colorization in terminals
Date: Wed, 12 Mar 2008 06:26:08 +0200 [thread overview]
Message-ID: <ubq5kk1pb.fsf@gnu.org> (raw)
In-Reply-To: <20080311231514.B718249C0BB@daedalus.stanford.edu>
> From: Rob Riepel <riepel@networking.stanford.edu>
> Date: Tue, 11 Mar 2008 16:15:14 -0700 (PDT)
> Cc:
>
> When using font-locking in a terminal window (xterm and the like)
> single-line comments are only highlighted to the first non-space
> character after a space. This happens in more than one language-
> specific mode - I've tried Emacs-lisp and CPerl modes.
>
> The bug does not occur when running Emacs under X, only in a terminal,
> and only for certain terminal types. The bug is present when TERM is
> set to xterm or xterm-color, but not when TERM is set to xterm-16color.
This is not a bug, but a deliberate feature. There's a new face named
font-lock-comment-delimiter-face.
next prev parent reply other threads:[~2008-03-12 4:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 23:15 incomplete comment colorization in terminals Rob Riepel
2008-03-12 4:26 ` Eli Zaretskii [this message]
2008-03-12 6:44 ` Dan Nicolaescu
2008-03-12 8:17 ` Nick Roberts
2008-03-12 13:54 ` Stefan Monnier
2008-03-12 15:07 ` Dan Nicolaescu
2008-03-12 17:51 ` Richard Stallman
2008-03-13 6:38 ` Dan Nicolaescu
2008-03-13 22:24 ` Richard Stallman
2008-03-13 22:44 ` Dan Nicolaescu
2008-03-14 0:21 ` Nick Roberts
2008-03-14 0:34 ` Dan Nicolaescu
2008-03-15 4:46 ` Nick Roberts
2008-03-15 8:34 ` Dan Nicolaescu
2008-03-15 0:49 ` Rob Riepel
2008-03-15 14:34 ` Eli Zaretskii
2008-03-12 4:45 ` Dan Nicolaescu
2008-03-12 13:57 ` Stefan Monnier
2008-03-13 6:40 ` Dan Nicolaescu
2008-03-13 15:01 ` Stefan Monnier
2008-03-13 18:55 ` Glenn Morris
2008-03-13 21:52 ` Dan Nicolaescu
2008-03-14 4:16 ` Dan Nicolaescu
2008-03-14 15:08 ` Stefan Monnier
2008-03-19 4:02 ` Dan Nicolaescu
2008-03-15 0:50 ` Rob Riepel
2008-03-12 13:10 ` Stefan Monnier
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=ubq5kk1pb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=riepel@networking.stanford.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).