After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 743842 - Parser used on non-saved files produces an incomprehensible error
Parser used on non-saved files produces an incomprehensible error
Status: RESOLVED FIXED
Product: bluefish
Classification: Other
Component: application
unspecified
Other Linux
: Normal normal
: 2.2.7
Assigned To: Bluefish Maintainer(s)
Bluefish Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-02-02 10:50 UTC by Paul Howarth
Modified: 2015-02-04 20:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paul Howarth 2015-02-02 10:50:07 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."
Comment 1 Olivier Sessink 2015-02-04 20:10:47 UTC
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)