https://bugzilla.redhat.com/show_bug.cgi?id=1003188 --- Comment #29 from Alex Villacís Lasso <a_villacis@xxxxxxxxxxxxx> --- I have just tested the 3.3.0-2 version. All files with a .php extension are recognized correctly. However, my projects have lots of PHP files that do not have a .php extension, such as "reconfigure-foo". These files are meant to be run from the command line and have PHP as a script interpreter. These files are initially not associated with any specialized editor. If I force the use of the PHP editor with such a file, a popup appear that states that the content type is not supported by the editor, and should be manually associated. After this, the file is opened with the default text editor, with no syntax highlighting or anything. This is the wrong behavior. If the user specified the PHP editor for the file, the plugin should just attempt to open the file with the PHP editor, no questions asked. This is the behavior of other language plugins in the system. -- You are receiving this mail because: You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review