2072 / vim-syntax-for-php Goto Github PK

Hello!

Is there any way to get back syntax highlighting for phtml files?

For template files where we mix HTML and PHP with this plugin it's only either PHP or HTML syntax highlighted.

Using the "built-in" php.vim syntax file does it correctly.

Thanks!

Hello!

I'd like to ask what should I change in this file so I can get an indentation for the witch construct like this:

// [ ... ]
    switch($var) {
        case 'a':
            do_something();
        break;
        case 'b':
            do_whatever_else();
        break;
        default:
            default_action();
        break; // optional
    }

As you can see, the break statement indents back to the case level, which is consistent with the fact that it "ends" the case block. It is also similar to other php syntaxes: if (): / else: / endif; or for (): / endfor;, etc.

I know this is not "standard" (PSRx), and I'm thinking about proposing it :), but since it is not, I would like to modify the syntax file to get this indentation scheme.

May you help me on this? I'm not proficient in vim script (I'm learning, just wrote a function 2 weeks ago :D), much less syntax files. O:)

Thank you.

Found this by accident, after disabling shorttags parsing after working a rather large file that caused syntax parsing to take a few seconds...

shorttags not disabled (that is, the default)

(note that these are not short tags, but echo tags)

with php_noShortTags=1

with php_noShortTags=1, if I remove the <?php tag

or make the end tag ?> be on a line with code (doesn't have to be a single line with the opening <?php tag. that code block can be any size, only the closing tag matters to not be alone on its own line)

short tags are also fine in terms of not messing with the other echo tags

but having that php tag anywhere breaks the echo tags parsing

note that this doesn't change when editing file. E.g. if I load a file in a working state (i.e. without the bug happening), it won't trigger the bug as i edit file, even if i add <?php and ?> closing on its own line. Only after i save and quit and reopen the file (or save and :e!). Likewise if i open a file with the bug, removing the trigger won't fix it, until I reload the file. Whatever is causing it is "sticky".