Bug 820038 - cperl-mode regression: poor handling of POD, here documents
cperl-mode regression: poor handling of POD, here documents
Product: Fedora
Classification: Fedora
Component: emacs (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Petr Hracek
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-05-08 20:37 EDT by Nick Urbanik
Modified: 2013-08-01 04:33 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-01 04:33:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nick Urbanik 2012-05-08 20:37:49 EDT
Description of problem:
cperl-mode loses "understanding" of Perl syntax in a program with POD (Plain old documentation) or with here document quoting of strings.  Both syntax highlighting and indentation become confused, requiring me to reload cperl-mode with the cursor in the "misunderstood" code.  This is particularly the case with POD written in a number of places in the code.

Version-Release number of selected component (if applicable):

How reproducible:
Too easily.

Steps to Reproduce:
1. Install perl-App-cpanminus-1.5007-2.fc17.noarch
2. open /usr/bin/cpanm in emacs (configured to use cperl-mode)
3. Note the syntax highlighting is broken after the POD.
Actual results:
Perl code after POD (and after some here document quoted strings) loses its syntax highlighting, and occasionally the indentation is made wrongly as you write code.

Expected results:
cperl-mode work at least as well as it did in earlier emacses (with version 23 on Fedora 16)

Additional info:
I have some additional code in one of my elisp files:
; Set indent style with indent of 4:
  '(cperl-close-paren-offset -4)
  '(cperl-continued-statement-offset 4)
  '(cperl-indent-level 4)
  '(cperl-indent-parens-as-block t)
  '(cperl-electric-parens nil)
  '(cperl-tab-always-indent t))

(add-hook 'cperl-mode-hook 'flyspell-prog-mode)

 (lambda (pair)
   (if (eq (cdr pair) 'perl-mode)
       (setcdr pair 'cperl-mode)))
 (append auto-mode-alist interpreter-mode-alist))
Comment 1 Nick Urbanik 2012-05-08 21:19:14 EDT
The use of apostrophes in POD affects the way that cperl-mode
interprets code that follows.
Comment 2 Fedora Admin XMLRPC Client 2013-02-27 10:47:20 EST
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Fedora End Of Life 2013-07-03 22:31:38 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2013-08-01 04:33:55 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.