From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Elisp syntax hilighting problem
Date: Sun, 23 Apr 2006 01:22:25 +0200 [thread overview]
Message-ID: <444ABAB1.3000807@student.lu.se> (raw)
In-Reply-To: <jek69hej8y.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
>
>
>> The defconst below sometimes upset the syntax highlighting so that the
>> function following it is in the same face as the string:
>>
>
> I cannot reproduce that here. Can you give more details about the
> situation where it occurs?
>
I happens sometimes but not always. One way I have seen to reproduce it
is to delete the line after defconst and before next declaration. I just
tested it - it worked for me a couple of times (ie I could see the
problem) and then everything looked ok again.
>
>> (defconst rng-in-attribute-value-regex
>> (replace-regexp-in-string
>> "w"
>> xmltok-ncname-regexp
>> "<w\\(?::w\\)?\
>> \\(?:[ \t\r\n]+w\\(?::w\\)?[ \t\r\n]*=\
>> [ \t\r\n]*\\(?:\"[^\"]*\"\\|'[^']*'\\)\\)*\
>> [ \t\r\n]+\\(w\\(:w\\)?\\)[ \t\r\n]*=[ \t\r\n]*\
>> \\(\"[^\"]*\\|'[^']*\\)\\="
>> t
>> t))
>>
>>
>> More problems: The \\= is not marked.
>>
>
> There are no builtin rules for marking this. Only grouping constructs
> have special faces.
>
Oh, I see. Maybe it should be marked?
>
>> The two [ at beginning of line is marked with a red face.
>>
>
> This is a feature. It marks characters (by default those of open paren
> syntax at the start of a line) that breaks the simple-minded parsing of
> beginning-of-defun. Prepend a backslash to avoid that.
>
Thanks.
next prev parent reply other threads:[~2006-04-22 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 0:16 Elisp syntax hilighting problem Lennart Borgman
2006-04-22 15:13 ` Andreas Schwab
2006-04-22 23:22 ` Lennart Borgman [this message]
2006-04-23 14:05 ` 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=444ABAB1.3000807@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=emacs-devel@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 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).