From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Will Willis Newsgroups: gmane.emacs.help Subject: Re: [cperl-mode] fontification problem with PODs Date: Fri, 30 Oct 2009 23:15:58 -0500 Message-ID: <6ee1e6090910302115g26189ceew972fffc771c3e9ea@mail.gmail.com> References: <91a903ec-dfbe-4f8c-b607-4253d832e0d1@m20g2000vbp.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001485f6da62c77b5c0477336609 X-Trace: ger.gmane.org 1256962598 18867 80.91.229.12 (31 Oct 2009 04:16:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 31 Oct 2009 04:16:38 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Oct 31 05:16:31 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 1N45OA-00042a-Mf for geh-help-gnu-emacs@m.gmane.org; Sat, 31 Oct 2009 05:16:31 +0100 Original-Received: from localhost ([127.0.0.1]:43465 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N45O9-0005is-G8 for geh-help-gnu-emacs@m.gmane.org; Sat, 31 Oct 2009 00:16:29 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N45Nj-0005hk-03 for help-gnu-emacs@gnu.org; Sat, 31 Oct 2009 00:16:03 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N45Ni-0005hL-Bw for help-gnu-emacs@gnu.org; Sat, 31 Oct 2009 00:16:02 -0400 Original-Received: from [199.232.76.173] (port=56148 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N45Ni-0005hH-7x for help-gnu-emacs@gnu.org; Sat, 31 Oct 2009 00:16:02 -0400 Original-Received: from fg-out-1718.google.com ([72.14.220.154]:40493) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N45Nh-0005p4-Ot for help-gnu-emacs@gnu.org; Sat, 31 Oct 2009 00:16:02 -0400 Original-Received: by fg-out-1718.google.com with SMTP id e21so81207fga.12 for ; Fri, 30 Oct 2009 21:15:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=BNfGbl+0MYgXp+7KUUObcdyOGX99ApjiVvLBmV/PE2U=; b=IH99NsGnQJrd6UwrGlxxO6Gm7depljmn486Tu1M7j67BQk+4VUcW4zzjGmueK3mZQT ogfcZs2MRGKJ2QXA9MXBa0DaEkek5rXW3DDpY7opQ/9oBPRe11tknM6OxvHjxsWoBNXA vBXGt5mXSRBxv4NpYv4FjPY3N8gTuCaLCXM+A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=M8ASb9GavtkTL1xws7BQOBcM7WkPBa2O3LURKFqSM1ZsRheBPamINRv/n9WwTayXxg ykOAuFeBakYwhKMG5AP9BkeznPMIBpqT8R2B6g3IUzXLZONvx5bwk/CRYAbB8qQBCywR DQS2w9PhIEEsv7BC9wWhXNEjkiy5zdyWcIXBw= Original-Received: by 10.239.139.134 with SMTP id t6mr263045hbt.12.1256962558228; Fri, 30 Oct 2009 21:15:58 -0700 (PDT) In-Reply-To: X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) 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:69368 Archived-At: --001485f6da62c77b5c0477336609 Content-Type: text/plain; charset=ISO-8859-1 over the years I've had to do alot of repeated M-x cperl-mode whilst coding in perl scripts containing POD - as the syntax highlighting would get lost or confused part-way down the file (usually turning everything into the comment color). Just something I've dealt with and never really attempted to fix. I'm glad I'm not the only one having issues. -Will On Sat, Oct 24, 2009 at 1:12 AM, Ilya Zakharevich wrote: > On 2009-10-21, LanX wrote: > > In the following example the second line is not classified as pod but > > the keyword "for" is considered part of a loop statement. > > Since it is not POD, I do not see any problem > > > -------------------------- > > lanx@nc10-ubuntu:~/tmp$ cat perlpod.pm > > for (1..9) {print} > >=for comment > > > It seems that loading another cperl-mode version causes conflicts with > > the bundled version! > > This may happen if the buggy version is preloaded... [I do not see > any problem with my version, both with emacs v19 and v21.] > > > So effectively one has to stick with the bundled version ... :( > > One may try to remove the buggy version from preloaded stuff (do not > remember how). > > Yours, > Ilya > --001485f6da62c77b5c0477336609 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable over the years I've had to do alot of repeated M-x cperl-mode whilst co= ding in perl scripts containing POD - as the syntax highlighting would get = lost or confused part-way down the file (usually turning everything into th= e comment color). Just something I've dealt with and never really attem= pted to fix.

I'm glad I'm not the only one having issues.

-Will

On Sat, Oct 24, 2= 009 at 1:12 AM, Ilya Zakharevich <nospam-abuse@ilyaz.org> wrote:
On 2009-10-21, LanX <<= a href=3D"mailto:lanx.perl@googlemail.com">lanx.perl@googlemail.com>= wrote:
> In the following example the second line is not classified as pod but<= br> > the keyword "for" is considered part of a loop statement.
Since it is not POD, I do not see any problem

> --------------------------
> lanx@nc10-ubuntu:~/tmp$ cat perlpod.pm
> for (1..9) {print}
>=3Dfor comment

> It seems that loading another cperl-mode versi= on causes conflicts with
> the bundled version!

This may happen if the buggy version is preloaded... =A0[I do not see=
any problem with my version, both with emacs v19 and v21.]

> So effectively one has to stick with the bundled version ... :(

One may try to remove the buggy version from preloaded stuff (do not<= br> remember how).

Yours,
Ilya

--001485f6da62c77b5c0477336609--