Recent changes to bugs

# comments don't highlight properly

Squid — Tue, 15 Feb 2011 04:23:47 -0000

any comment started with a # gets overridden with the highlighting of any word inside that comment that is covered by another highlighting rule

e.x. # if the display group is a new group, then

The 'if', ',' and 'then' are all not coloured as comments.

E_DEPRECATED and other constants mishighlighted

Nathan Phillip Brink — Tue, 14 Sep 2010 16:10:42 -0000

All of the magic constants listed here are not correctly highlighted: http://docs.php.net/manual/en/language.constants.predefined.php

Also, E_STRICT and E_DEPRECATED (relatively new constants) are not correctly highglighted.

php-mode can crash emacs 23.1

Anonymous — Tue, 22 Dec 2009 14:09:44 -0000

PHP-mode-1.5.0's been crashing emacs 23.1. I can trigger this behaviour by entering PHP-mode, then typing
function test($one,

at which point the wrist-watch cursor shows up, and emacs is dead.

I submitted a bug to emacs (5258). See http://lists.gnu.org/archive/html/bug-gnu-emacs/2009-12/msg00613.html for a very long abridged backtrace. It looks like the garbage-collector gets stuck in a loop. I'm not familiar with debugging emacs, so I can't suggest what line of elisp is causing the fail. Previous versions of emacs are not affected.

PHP keyword not found

Anonymous — Fri, 18 Dec 2009 08:32:17 -0000

The switch statement contains php keyword 'default' that is not defined in the php-keywords list

Multiline array and fluent interface indentation fails

trashofmasters — Tue, 08 Dec 2009 20:38:05 -0000

Sorry if I posted as Nobody the earlier, this is the first time I'm using this Issue Tracker

PHP Mode 1.5.0 suffers of different indentation issues related to the PEAR coding standard
when indenting multiline array definitions, fluent interfaces and function arguments.

The file attached contains the proper report with examples of actual and expected behaviour.

Array and fluent interfaces fails

Anonymous — Tue, 08 Dec 2009 20:32:17 -0000

Indentation fails to follow PEAR coding standards:

arrays are indented using relative position of opening bracket
instead of indenting of +4 spaces, thus leading to exceed the
80 characters limit pretty fast.

Actual behaviour:
$longNameForPointLessArray = array(
0 => null,
1 => array(
0 => null
)
);

Expected behaviour:
$longNameForPointLessArray = array(
0 => null,
1 => array(
0 => null
)
);

When function arguments are spanned across multiple lines they seem
to suffer from the very same issue.

A similar issue is present when using fluent interfaces spanned
over multiple lines. The arrow operators should be aligned in
a row.

Actual behaviour:
$aObject = new Class();
$aObject->aMethod()
->anotherMethod()
->anotherMethod();

Expected behaviour:
$aObject = new Class();
$aObject->aMethod()
->anotherMethod()
->anotherMethod();

PHP-mode uses up to 100% CPU

Paul Ebermann — Fri, 27 Nov 2009 16:13:29 -0000

I recently installed PHP-mode (the version with "Modified: 2008-11-04", with the manual for "1.5.0").
Since then the Emacs uses up to 100% CPU when viewing/editing an PHP file. (It usually starts at a low value like 20% and goes up, sometimes a bit down for a while, depending on the other programs I have.)

A sample file is this one:
---
<?php

?>
---
But even an empty file shows the same symptoms, or the files I regularily work on.

This is mostly when such a PHP file is in the active buffer, but sometimes also when it is more back in the buffer list. killing the buffer solves the problem, as sometimes also does burying the buffer.

This should not be this way, I think.

Here is my Emacs-info:
GNU Emacs 22.3.1 (i586-suse-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2008-12-03 on build19

PHP-mode uses up to 100% CPU

Paul Ebermann — Fri, 27 Nov 2009 15:59:33 -0000

A sample file is this one:
---
<?php

?>
---
But even an empty file shows the same symptoms, or the files I regularily work on.

This should not be this way, I think.

Here is my Emacs-info:
GNU Emacs 22.3.1 (i586-suse-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2008-12-03 on build19

switch default case syntax marked as invalid

ingvar harjaks — Thu, 03 Sep 2009 12:51:00 -0000

Example:
switch ($whatever) {
case 1: break;
default:
}
Then "default" is marked as red - invalid syntax.

I'm using emacs 23 with php-mode 1.2.0 of 2008-11-04

find-tag-noselect doesn't exist in etags.el

Anonymous — Sat, 25 Jul 2009 20:03:59 -0000

find-tag-noselect is called but I can't find it anywhere.