Thanks for adding support for this!

But unfortunately, I can’t get it to work. When I launch the Pology check, nothing seems to happen. But I do get this error message on the terminal:

posieve: [error] 'ascii' codec can't decode byte 0x86 in position 25: ordinal not in range(128)

Some other issues: If you try to launch the check without having specified a Pology command in the settings, no error message is shown. Preferably, the menu-option should be greyed out in this case (but still visible, to make the feature more discoverable).

Also, if you disable the Pology support, the ‘Launch the Pology command on this file’ menu-item is still enabled on the ‘File’ menu.

Also, for the example command line, check_rules should be check-rules (though both work). And the command should point to bin/posieve instead of scripts/posieve.py. But I really think the default should just be to call the correct posieve command (with the needed parameters) automatically (given that the user has the Pology tools installed). Having to specify the command-line manually should only be needed if the user wants to use some fancy filtering of messages or rule sets, or if they haven’t installed Pology at all (or in a non-PATH location).

And though I can see a use case for having different settings (e.g. rule sets) for different project, I think this is a rather rare case, and that the Pology settings belong in the main preferences instead (or possibly with per-project overrides).

As for displaying the results, having a separate ‘Pology results’ pane showing the results would be nice (click on an error to jump to the message with the error).

And perhaps a ‘Pology errors’ column in the Project View (which would show the number of errors in each file – ‘0’ if no errors, ‘–’ if the file hasn’t been checked yet, or if it has been changed since the last check).

In D15759#332366, @huftis wrote:

As for displaying the results, having a separate ‘Pology results’ pane showing the results would be nice (click on an error to jump to the message with the error).

And perhaps a ‘Pology errors’ column in the Project View (which would show the number of errors in each file – ‘0’ if no errors, ‘–’ if the file hasn’t been checked yet, or if it has been changed since the last check).

For now I just want to leverage on the "-s lokalize" feature of pology which interacts with lokalize, having the number of errors is definitely something I want to add but I'm not sure how to proceed yet

I've made the following changes :

• Moved the config from project to application
• Set up default values for the command lines
• Gray out the option in the editor tab when pology is disabled
• Add a pop-up on success (else you don't know when it's over)

• Redirect error messages

• Escaping the file names with double-quotes (maybe that's where your problem is coming from, now the command line is output if you launch from a terminal so you should be able to try the command manually)

How does this ‘fix’ https://bugs.kde.org/show_bug.cgi?id=198872?