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: [alinsoar@voila.fr: this is a bug?]
Date: Tue, 27 Mar 2007 12:10:44 +0200 (CEST)	[thread overview]
Message-ID: <28338702.917781174990244387.JavaMail.www@wwinf4206> (raw)

> >I report again, becuase this bug was ignored.
> 
> In fact, I had answered to you, but received no reply.  I append the
> text of my previous mail at the end of this mail.

Sorry, I found all these messages in spam, and corbeille, because it was automatically deleted.

> 
> > I rewrite it into an easier to reproduce form:
> >1. Emacs -Q
> >2. M-. Lisp_Type <RET>
> >Select then the path to your TAGS file of your emacs.
> 
> All well until here.


> 
> >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?
> 
> What I see is that the buffer shows the lisp.h file, and the cursor is
> at the line of the definition of "enum Lisp_Type", which is what I
> expect.
> 
> >So this is a bug.
> 
> I cannot reproduce it.  After the second step of you description, what
> path do you enter?  What do you see exactly after that?  Does Emacs open
> the lisp.h file?


The problem is just about the definition of FONT LOCK of C mode.

Why the first 4 members are yellow,Lisp_Int,Lisp_Symbol,Lisp_Misc,Lisp_String,
and the last 4 members are white? This is a bug evidently in FONT LOCK.

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 10:10 A Soare [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-27 11:05 [alinsoar@voila.fr: this is a bug?] A Soare
     [not found] <E1HVyOi-0001PT-Cm@fencepost.gnu.org>
2007-03-27  6:52 ` Francesco Potorti`

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=28338702.917781174990244387.JavaMail.www@wwinf4206 \
    --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.