unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rob Riepel <riepel@networking.stanford.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-pretest-bug@gnu.org, Dan Nicolaescu <dann@ics.uci.edu>
Subject: Re: incomplete comment colorization in terminals
Date: Fri, 14 Mar 2008 17:50:18 -0700	[thread overview]
Message-ID: <98D9DE3A-9F52-402B-9CF3-6B8F29BDA8AC@networking.stanford.edu> (raw)
In-Reply-To: <jwvlk4ot5ce.fsf-monnier+emacs@gnu.org>

On Mar 12, 2008, at 6:57 AM, Stefan Monnier wrote:

> The NEWS entry for f in Emacs-22 is insufficient I believe.  It  
> should explain the effect of the introduction of this new face and  
> should point to xterm-256color as well as other methods to recover  
> the previous behavior.

The new entry looks great.  You may want to mention font-lock-comment- 
delimiter-face in the font-lock-mode documentation.  Right now it says:

| When Font Lock mode is enabled, text is fontified as you type it:
|
|  - Comments are displayed in `font-lock-comment-face';
|  - Strings are displayed in `font-lock-string-face';

Which could be slightly confusing to those who don't know that the  
delimiter is not part of the comment (at least as far as  
fontification is concerned).

--
Rob Riepel
(650) 725-7577
http://geek.stanford.edu






  parent reply	other threads:[~2008-03-15  0:50 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
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 [this message]
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=98D9DE3A-9F52-402B-9CF3-6B8F29BDA8AC@networking.stanford.edu \
    --to=riepel@networking.stanford.edu \
    --cc=dann@ics.uci.edu \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).