[Github-comments] [geany/geany] Track changes to line numbers for messages and compiler errors (#1481)

[Vasiliy Faronov]

@elextr In my experience, it is not so in Python. Firstly, there’s Find in Files, which is very important in refactoring — probably more so than in C++, because you can’t just break things and expect the compiler to point out the places to fix. Secondly, compiler errors usually don’t come from actually running the program, but rather from static analysis tools such as Pylint and Mypy. The problems they report are often independent from each other.

However, I understand your point.

Would your opinion change if I went the indicators or line markers route instead? In that case, there would be little to no overhead during editing, because Scintilla would be keeping track of changes for us. (In fact, of course, Geany already marks errors with indicators — just not in a way that is immediately reusable for this purpose.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/1481#issuecomment-298157323
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20170429/627482d3/attachment.html>