From: Dan Nicolaescu <dann@ics.uci.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: Rob Riepel <riepel@networking.stanford.edu>,
emacs-pretest-bug@gnu.org,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: incomplete comment colorization in terminals
Date: Thu, 13 Mar 2008 21:16:44 -0700 [thread overview]
Message-ID: <200803140416.m2E4GiKr016910@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <kqprtypi7a.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 13 Mar 2008 14:55:21 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Stefan Monnier wrote:
>
> >> Should we add a new entry for emacs-22.2 to correct these issues?
> >
> > Yes, please.
>
> I already did.
Wouldn't it be better if the new text you added be in the 22.2 section?
It's not very likely that 22.1 users would read pass the 22.2 section.
Just add a note that this has been present in 22.1 too.
next prev parent reply other threads:[~2008-03-14 4:16 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200803140416.m2E4GiKr016910@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@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 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.