After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 323998 - perl "here doc" not highlighted
perl "here doc" not highlighted
Status: RESOLVED FIXED
Product: gtksourceview
Classification: Platform
Component: Syntax files
1.4.x
Other Linux
: Normal normal
: ---
Assigned To: GTK Sourceview maintainers
GTK Sourceview maintainers
Depends on:
Blocks:
 
 
Reported: 2005-12-13 18:02 UTC by Jaap Karssenberg
Modified: 2014-02-15 12:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jaap Karssenberg 2005-12-13 18:02:32 UTC
Version details: 1.4.2

"Here doc" constructs in perl are not highlighted:

  my $var = << "EOT";
  some plain text
  here
  EOT

The text on the lines belonging to the here-doc should be highlighted as quoted
text (double-quoted in this case, single-quoted in other cases).
Comment 1 Paolo Maggi 2005-12-28 14:03:26 UTC
May you please provide a patch?
Comment 2 Paolo Maggi 2005-12-30 14:44:18 UTC
I have looked more deeply at the problem you reported.
It is not possibile to fix it with the current hl engine. We will fix it with
the new hl engine.
Comment 3 Steve Frécinaux 2006-03-20 08:47:58 UTC
Just for note, same problem exists with PHP and maybe (not tested) for Shell.
Comment 4 Steve Frécinaux 2007-01-08 00:19:28 UTC
As a test case for the new hl engine: I've noticed this piece of code I wrote is not highlighted correctly by vim. Maybe we could do better ? ;-)

print <<EOF and exit if $help;
Usage: git-send-bugzilla [options] <since>[..<until>]
EOF

Thus here, the lines 2 and 3 should be highlighted as a string, as <<EOF, but "and exit if $help" should be highlighted as Perl code. Vim highlights it as a string.
Comment 5 Steve Frécinaux 2007-07-04 10:41:28 UTC
There is a patch for that attached to bug #453638
Comment 6 Steve Frécinaux 2007-07-13 16:05:45 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.