Revs af8958 and 1c728f have removed some hangnails concerning pyflakes and
pylint messages.
The pyflakes messages in particular were terribly confusing. The culprit:
calling pyflakes *before* saving the file, which checked the old code!
Both pyflakes and pylint now indicate the program producing the message.
This is needed now that pylint runs in the background.
I now use the following settings:
@bool run-pyflakes-on-write = True
@bool syntax-error-popup = True
The first runs pyflakes on all changed files just after they have been
written or created. The second raises an error dialog if either pylint or
pyflakes detects an error. Now that pyflakes is running so often, I find I
need the dialog to draw my attention to errors. YMMV.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
