unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jie Zhang" <jzhang918@gmail.com>
Cc: acm@muc.de, mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org
Subject: Re: Problem report: No syntax highlight for C
Date: Sun, 4 Jun 2006 01:30:31 +0800	[thread overview]
Message-ID: <6f48278f0606031030q3daf3f2p64b702e91ad9fec6@mail.gmail.com> (raw)
In-Reply-To: <u8xoecp2q.fsf@gnu.org>

On 6/3/06, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sat, 3 Jun 2006 19:59:10 +0800
> > From: "Jie Zhang" <jzhang918@gmail.com>
> > Cc: emacs-devel@gnu.org, acm@muc.de, mituharu@math.s.chiba-u.ac.jp, rms@gnu.org
> >
> > > > > Is this in "emacs -Q"?  If so, I cannot reproduce this.  Do you have
> > > > > any messages in the *Messages* buffer that could shed a light on the
> > > > > reason(s)?
> > > > >
> > > > I'm rather new to emacs. I don't know what exactly "emacs -Q" meas.
> > > > Does it means passing -Q to emacs while invoking it?
> > >
> > > Yes, it means invoke Emacs with the -Q command-line switch.
>
> You didn't say if the problem happens with -Q.  Please do.
>
It happens with -Q.

> > > If using -Q doesn't make this problem go away, please tell how up to
> > > date is your Emacs code.  If you checked out the CVS tree yourself,
> > > please tell at what date you did that.  If you got the sources from
> > > someone else, please tell what is the first entry that you see in the
> > > file lisp/ChangeLog.
>
> You didn't reply to this.  Please do.
>
I'm using the CVS code checked out today. Actually, this problem
exists for me since the code checked out using -D20060525 or later.
The first entry in lisp/ChangeLog in my code is:

2006-06-03  Vivek Dasmohapatra  <vivek@etla.org>

        * progmodes/sh-script.el (sh-quoted-exec): New face for quoted
        exec constructs like `foo bar`.
        (sh-quoted-subshell): New helper function to search for a possibly
        nested subshell (like `` or $()) within a "" quoted string.
        (sh-font-lock-keywords-var): Add sh-quoted-exec for Bash.
        (sh-apply-quoted-subshell): Flag quote characters inside a
        subshell, which is itself already in a quoted region, as
        punctuation, since this is the closest to what they actually are.
        (sh-font-lock-syntactic-keywords): Add sh-quoted-subshell and
        sh-apply-quoted-subshell.
        (sh-font-lock-syntactic-face-function): Apply the new face for
        text inside `` instead of the old font-lock-string-face.

> > I have narrowed down the changes which cause this issue. The CVS on
> > 20060524 has no such issue, but 20060525 does. There are two and half
> > entries which were added between these two dates. I add their owners
> > to the CC list. Hope this help.
>
> This doesn't explain why I don't see the problem on my machine, with
> today's CVS.  Do you have this problem with every .c file, or just
> with some?  If the latter, please post the smallest .c file which
> causes the problem.
>
I have this problem in every .c file I opens. I'm using Ubuntu Dapper,
which is upgraded everyday. I checked out emacs from
":pserver:anonymous@cvs.savannah.gnu.org:/sources/emacs".

Jie

  reply	other threads:[~2006-06-03 17:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-02 17:07 Problem report: No syntax highlight for C Jie Zhang
2006-06-02 17:55 ` David Kastrup
2006-06-02 21:03 ` Eli Zaretskii
     [not found]   ` <6f48278f0606021759raaa2f9an793e07bd7cb23347@mail.gmail.com>
2006-06-03  7:59     ` Eli Zaretskii
2006-06-03 11:59       ` Jie Zhang
2006-06-03 14:05         ` Eli Zaretskii
2006-06-03 17:30           ` Jie Zhang [this message]
2006-06-03 18:17             ` Eli Zaretskii
2006-06-04 15:04               ` Jie Zhang
2006-06-04 18:48                 ` Eli Zaretskii
2006-06-05  4:44                   ` Jie Zhang
2006-06-05 19:27                     ` Eli Zaretskii
2006-06-06  5:52                       ` Jie Zhang
     [not found]       ` <20060603105839.GA1078@muc.de>
2006-06-03 12:15         ` Jie Zhang

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=6f48278f0606031030q3daf3f2p64b702e91ad9fec6@mail.gmail.com \
    --to=jzhang918@gmail.com \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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).