GNOME Bugzilla – Bug 743842
Parser used on non-saved files produces an incomprehensible error
Last modified: 2015-02-04 20:10:47 UTC
Forwarded from https://bugzilla.redhat.com/show_bug.cgi?id=1119520 Using a parser in submenu Output parsers on a non-saved file produces an error: 1. Open Bluefish 2. File → new from template → XHTML 1.0 3. Tags → Headings → H1 (For instance) 4. Write a word in the h1 tag. 5. Tools → Output parsers → xmllint XML checker Actual results: "Failed to create a command for xmllint --noout --valid '%f'|." The same thing occurs if, instead of a XHTML file, you create a new PHP file and launch "php syntax check". In this case, the result is: "Failed to create a command for php -l -q -f '%f'|." Expected results: The checker should work even if the file is not saved, or, at least, the error message should be clear: "The checker only works on saved files. Please save your file first."
Thanks for reporting this. The error messages for all possible errors have been improved. This particular error now results in this message: This command requires the current document to have a file name. Please save your document first. It will be included in 2.2.8 (2.2.7 has been released a few days ago)