Your message dated Wed, 4 Jul 2012 15:40:05 +0100
with message-id
<CAPQ4b8keBuSM7-ysaqxXdQuAmvDAU=apndyotwpkh2ucv15...@mail.gmail.com>
and subject line Closing orphan/obsolete bugs (emacs21-el with tag
unreproducible or fixed-upstream)
has caused the Debian Bug report #270543,
regarding emacs21-el: perl-mode.el font-lock for =item ... blocks
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
270543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=270543
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: emacs21-el
Version: 21.3+1-7
Severity: minor
Tags: patch
If a Perl file has the following structure:
=item ...
...
=cut
within it, not immediately beginning with a =head1 or =pod, then the
syntactic hilighting fails. (See, for example, /usr/bin/bts in
devscripts, which is where this bug report originated.)
This patch fixes this, by accepting any POD introductory string as the
start of a b-style comment.
--- perl-mode.el.orig 2004-09-07 21:31:57.000000000 +0100
+++ perl-mode.el 2004-09-07 21:36:15.000000000 +0100
@@ -219,7 +219,7 @@
(defvar perl-font-lock-syntactic-keywords
;; Turn POD into b-style comments
- '(("^\\(=\\)\\(head1\\|pod\\)\\([ \t]\\|$\\)" (1 "< b"))
+
'(("^\\(=\\)\\(head[1-4]\\|over\\|item\\|back\\|pod\\|begin\\|end\\|for\\)\\([
\t]\\|$\\)" (1 "< b"))
("^=cut[ \t]*\\(\n\\)" (1 "> b"))
;; Catch ${ so that ${var} doesn't screw up indentation.
("\\(\\$\\)[{']" (1 "."))))
Julian
--- End Message ---
--- Begin Message ---
Hello,
Thanks for your interest in improving Debian, and sorry that the bugs
were not fully resolved in due time.
emacs21 packages have been removed from testing in 2009 [1], not
present even in the current stable. Consequently, these bugs are now
orphan (without maintainer assigned) so they probably will not be
attended/noticed further.
[1] http://packages.qa.debian.org/e/emacs21.html
The bugs deemed valid are going to be verified and reassigned, but the
current bugs that I'm closing now are very ancient (more than 10 years
sometimes) and marked as unreproducible or fixed upstream years ago.
Please comment if you want think that some of the raised questions are
still pending and need to be addressed differently (e.g., reassigned
to other packages, etc.).
Cheers.
--- End Message ---
