From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Joseph Brenner Newsgroups: gmane.emacs.help Subject: Re: [cperl-mode] fontification problem with PODs Date: Sun, 06 Dec 2009 16:12:24 -0800 Message-ID: <87bpibd4lz.fsf@kzsu.stanford.edu> References: <91a903ec-dfbe-4f8c-b607-4253d832e0d1@m20g2000vbp.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1260146456 9686 80.91.229.12 (7 Dec 2009 00:40:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Dec 2009 00:40:56 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Dec 07 01:40:49 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NHRei-0007eP-7g for geh-help-gnu-emacs@m.gmane.org; Mon, 07 Dec 2009 01:40:48 +0100 Original-Received: from localhost ([127.0.0.1]:49096 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NHReh-0002MI-FP for geh-help-gnu-emacs@m.gmane.org; Sun, 06 Dec 2009 19:40:47 -0500 Original-Path: news.stanford.edu!usenet.stanford.edu!news.glorb.com!news2.glorb.com!news.glorb.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.posted.rawbandwidth!news.posted.rawbandwidth.POSTED!not-for-mail Original-NNTP-Posting-Date: Sun, 06 Dec 2009 18:11:11 -0600 Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:8j36dZVltzQb+m2roKgYcq4EC/0= Original-Lines: 55 X-Usenet-Provider: http://www.giganews.com Original-NNTP-Posting-Host: 198.144.208.84 Original-X-Trace: sv3-9C8uqM31bZd3ct5P9c9329FL/1ol2yJSWsZeIeHYFLuHKHvSsq/i+bUTnV48k5FvEjy0qdTim7yp3a3!vEGqSd3WVhUtGKpWtsDKewXilYcWMxiZ/akD+JZjoxw2YrqryBbn5CaBM37hJR9J1jyQjdKcctU= X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 Original-Xref: news.stanford.edu gnu.emacs.help:175387 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:70463 Archived-At: LanX 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 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.