From: Joseph Brenner <doom@kzsu.stanford.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: [cperl-mode] fontification problem with PODs
Date: Sun, 06 Dec 2009 16:12:24 -0800 [thread overview]
Message-ID: <87bpibd4lz.fsf@kzsu.stanford.edu> (raw)
In-Reply-To: 91a903ec-dfbe-4f8c-b607-4253d832e0d1@m20g2000vbp.googlegroups.com
LanX <lanx.perl@googlemail.com> writes:
> I experienced a problem with the fontification of POD's.
>
> In the following example the second line is not classified as pod but
> the keyword "for" is considered part of a loop statement.
>
> --------------------------
> lanx@nc10-ubuntu:~/tmp$ cat perlpod.pm
> for (1..9) {print}
> =for comment
>
> This B<document> is in Pod format. To read this, use a Pod formatter,
> like "perldoc perlpod".
>
> =cut
> ---------------------------
>
> which might be OK since there is an empty line missing between POD and
> code.
>
> So adding a newline at the second line should solve the problem, but
> doesn't do so!!!
I was going to point out the same thing, but also, I recommend running
the "podchecker" program occasionally.
pod is cool, but very wasteful of vertical whitespace, and weirdly
enough it's whitespace sensitive: it wants completely empty blank lines
before and after the tags -- blank lines with spaces on them are not
good enough.
> Strangely this problem is NOT present when calling emacs with -Q
>
> ---------------------------
> lanx@nc10-ubuntu:~/tmp$ emacs -Q perlpod.pm -f cperl-mode
> ---------------------------
>
> So adding the newline solves the problem!
> And calling "M-x describe-text-properties" shows that the POD-text is
> classified as such.
This is indeed sounding pretty weird.
> It seems that loading another cperl-mode version causes conflicts with
> the bundled version!
>
> So effectively one has to stick with the bundled version ... :(
Well... I might suspect a conflict between something else you normally
load and cperl-mode. It's difficult to say what... remember that emacs
has just one big global namespace, so hypothetically all sorts of
action-at-a-distance problems are possible with poorly written elisp.
next prev parent reply other threads:[~2009-12-07 0:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 13:36 [cperl-mode] fontification problem with PODs LanX
2009-10-24 6:12 ` Ilya Zakharevich
2009-10-31 4:15 ` Will Willis
2009-12-07 0:12 ` Joseph Brenner [this message]
2009-12-09 12:49 ` LanX
2010-05-02 4:32 ` Ilya Zakharevich
2010-05-02 14:07 ` Alan Mackenzie
2010-05-04 3:33 ` Ilya Zakharevich
2010-05-04 10:39 ` Alan Mackenzie
2010-05-04 14:55 ` LanX
2010-05-06 20:08 ` Ilya Zakharevich
2010-05-07 1:31 ` Juanma Barranquero
[not found] ` <mailman.29.1273195927.9285.help-gnu-emacs@gnu.org>
2010-05-07 2:55 ` Stefan Monnier
2010-05-08 21:50 ` Juanma Barranquero
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=87bpibd4lz.fsf@kzsu.stanford.edu \
--to=doom@kzsu.stanford.edu \
--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.