all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: A Soare <alinsoar@voila.fr>
To: Francesco Potorti` <pot@gnu.org>
Cc: "Emacs   Dev  \[emacs-devel\]" <emacs-devel@gnu.org>
Subject: Re: C font-lock bug
Date: Fri, 27 Apr 2007 12:32:08 +0200 (CEST)	[thread overview]
Message-ID: <1340097.281321177669928471.JavaMail.www@wwinf4201> (raw)

> Sorry for the big delay, I am trying ot recover my email backlog.
> 
> >> >1. Emacs -Q
> >> >2. M-. Lisp_Type <RET>
> >> >Select then the path to your TAGS file of your emacs.
> >> >The first 4 members of this enumeration are listed in yellow color to
> >> >me . The last 4 members in black color .
> >> 
> >> What enumeration?  Why are the colours important?
> >
> >Lisp_Type is an enumeration. And because It is preceded by M-. (i.e. by
> >find-tag) it is clear what it means.
> 
> At last I understand.  In fact, find-tag is completely unrelated with
> this.

I wrote it just to jump quickly to the Lisp_Type.

>  I changed the subject to reflect that this is a bug in font-lock
> for C code.

We got it. I repetead many times that.

> 
> Specifically, if you load lisp.h from the Emacs sources and look at
>  enum Lisp_Type
> you see that the colour of the members of the enum changes after the
> fourth member.

That was my bug that I reported 2 times in past.

Who solved it?


Alin Soare.

             reply	other threads:[~2007-04-27 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 10:32 A Soare [this message]
2007-04-27 11:19 ` C font-lock bug Francesco Potorti`
  -- strict thread matches above, loose matches on Subject: below --
2007-04-27 17:56 A Soare
2007-04-27 11:30 A Soare
2007-03-27 11:05 [alinsoar@voila.fr: this is a bug?] A Soare
2007-04-27 10:07 ` C font-lock bug Francesco Potorti`
2007-04-27 12:38   ` Alan Mackenzie

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=1340097.281321177669928471.JavaMail.www@wwinf4201 \
    --to=alinsoar@voila.fr \
    --cc=emacs-devel@gnu.org \
    --cc=pot@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.
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.