From: LanX <rolf.langsdorf@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: (cperl-mode) Problems with syntax highlighting after __DATA__ !
Date: Thu, 21 Oct 2010 04:43:43 -0700 (PDT) [thread overview]
Message-ID: <496a9e4f-414a-44c2-8f3e-a83071743a5c@a36g2000yqc.googlegroups.com> (raw)
In-Reply-To: 87wrpeqjkb.fsf@lifelogs.com
Hi
back again was travelling the last days...
> SM> Yes, of course: short of using multiple major modes (which is something
> SM> Emacs doesn't support very well for now), there's not much highlighting
> SM> we can do other than assuming Perl syntax.
>
> I think it's not that bad. __DATA__ is the same content (semantically)
> as a here-file,
or a POD-section , i.e. natural solution would be comment-face.
(like most other editors I tested do, just check vim)
__END__ is practically the same as __DATA__ and Ilya is right those
sections are terminated only by EOF.
@Stefan: I'm not talking about highlighting according to HTML just
wanna avoid the perl-parser to hang the system.
@Ilya: Sorry the HTML is confidential, I'm even not allowed to publish
parts of it, e.g. by stripping the text between the markup. :( And I
wasn't able to reproduce it.
FWIW my workaround at the moment is to start the __DATA__ section
with
----------
=pod
-----------
to avoid syntaxification.
next prev parent reply other threads:[~2010-10-21 11:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 12:22 (cperl-mode) Problems with syntax highlighting after __DATA__ ! LanX
2010-10-15 6:57 ` Ilya Zakharevich
2010-10-15 10:40 ` LanX
2010-10-15 13:14 ` LanX
2010-10-15 13:35 ` LanX
2010-10-15 13:35 ` LanX
2010-10-15 22:40 ` Ilya Zakharevich
2010-10-16 14:20 ` LanX
2010-10-17 2:56 ` Stefan Monnier
2010-10-19 15:38 ` Ted Zlatanov
2010-10-20 19:40 ` Ilya Zakharevich
2010-10-20 19:42 ` Ilya Zakharevich
2010-10-21 11:43 ` LanX [this message]
2010-10-22 15:57 ` Ted Zlatanov
2010-10-24 5:59 ` Ilya Zakharevich
2010-10-17 11:03 ` Ilya Zakharevich
2010-10-15 14:25 ` 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=496a9e4f-414a-44c2-8f3e-a83071743a5c@a36g2000yqc.googlegroups.com \
--to=rolf.langsdorf@googlemail.com \
--cc=help-gnu-emacs@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.