Description of problem: Using a parser in submenu Outputbox on a non-saved file produces an error. Version-Release number of selected component (if applicable): 2.2.6 How reproducible: Always Steps to Reproduce: 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 → Outputbox → xmlling 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." Additional info:
Raised upstream, still present in 2.2.7.
Upstream is going to fix this in the next release (2.2.8). 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.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Version-Release number of selected component (if applicable): 2.2.7
bluefish-2.2.8-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-5692cf7e86
bluefish-2.2.8-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-5692cf7e86
bluefish-2.2.8-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.