PHP Syntax Coloring Fails In Bluefish with Single-Line Comments

Bug #1263967 reported by linux4me
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bluefish
Fix Released
Medium
bluefish (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm running Ubuntu 13.10 and Bluefish 2.2.4. I'm using a clean install of Ubuntu with my old /home directory copied over after installation, including my .bluefish folder. Syntax coloring in PHP files fails whenever a single line comment using // or # precedes a codeblock without an intervening empty line.

In this example, all the code between the PHP tags appears gray:
<?php
// Here is a comment.
$var =
echo "The value is " . $var;
?>

However, if I put an empty line between the comment and the code, the code has the proper syntax highlighting:
<?php
// Here is a comment.

$var =
echo "The value is " . $var;
?>

You can see what I mean in the screenshot to follow.

If I use a # instead of //, the same problem occurs. If I use multi-line comments (/* and */), the syntax coloring is correct. Refreshing the syntax coloring with F5 makes no difference. I also renamed my .bluefish file and restarted Bluefish to see if some old setting was causing the issue, but the problem persisted. Bluefish seems to work fine otherwise, but I really miss my syntax coloring.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: bluefish 2.2.4-2
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Tue Dec 24 08:58:11 2013
InstallationDate: Installed on 2013-12-16 (7 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
SourcePackage: bluefish
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
linux4me (ta2008) wrote :
Revision history for this message
Nicola Quargentan (nicola-quargentan) wrote :

I confirm this bug also in Ubuntu 13.10 32 bit.

Thanks for the tip of the empy line: that saves my brain!
This little bug will greatly affect the use of bluefish.

Nicola.

Revision history for this message
linux4me (ta2008) wrote :

Thanks Nicola! I'm glad it's not just me.

I agree it really affects the use of Bluefish. I end up debugging a lot of other author's code, and the lack of the syntax coloring makes it a real pain.

Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

This has already been fixed upstream and will be shortly in the distributions too.

Changed in bluefish:
importance: Unknown → Medium
status: Unknown → Incomplete
Revision history for this message
linux4me (ta2008) wrote :

That's great news Daniel, thank you.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluefish - 2.2.5-1

---------------
bluefish (2.2.5-1) unstable; urgency=low

  * New upstream release.
    - Fixes a highlighting bug (LP: #1242387, #1263967).
  * debian/control (Standards-Version): Bumped to 3.9.5.
    (Build-Depends): Added dh-autoreconf and some GTK related version info.
  * debian/copyright: Fixed unversioned-copyright-format-uri.
  * debian/rules: Use the autoreconf addon (closes: #737671).
  * debian/upstream-signing-key.pgp: Added upstream keyring.
  * debian/watch: Added signature URL.
  * debian/source/include-binaries: Added debian/upstream-signing-key.pgp.

 -- Daniel Leidert <email address hidden> Tue, 11 Feb 2014 16:52:23 +0100

Changed in bluefish (Ubuntu):
status: New → Fix Released
Changed in bluefish:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.