GNU bug report logs -
#26850
perl-mode: apostrophes trigger color change in wrong situation
Previous Next
Reported by: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Date: Tue, 9 May 2017 05:44:01 UTC
Severity: minor
Tags: confirmed, fixed
Merged with 26745
Found in versions 27.0.50, 28.0.50
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #19 received at 26850 <at> debbugs.gnu.org (full text, mbox):
haj <at> posteo.de (Harald Jörg) writes:
> I don't know whether I have the authority to merge bugs, but they
> clearly are the same issue, so I'll just give it a try.
Oh, sure, I think everybody can. Hm... but it doesn't seem to have
gone through in this case? When the statuses of the bugs involved
aren't the same, you have to use "forcemerge" to make it actually
happened; I did that now.
> There are several workarounds: You could, for example, explicitly write
> the regexes as $_ =~ /.../; ... but of course, why would you do that,
> since $_ is superfluous. Alternatively, you could just omit the
> "return", which is also superfluous in the examples provided.
>
> Nevertheless, the patch fixes the issue, which happens in both perl-mode
> and cperl-mode. I guess that in neither mode the list of keywords which
> precede a regex is actually complete, but "return" is a use case
> relevant enough to be fixed.
Thanks for the patch; applied to Emacs 28.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
This bug report was last modified 4 years and 185 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.