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

[elextr]

I guess it depends on the language you are using and how it works, but for me (in C++) after the first few errors too many are consequential errors (things that are only wrong because of a previous error).  So going beyond the first few errors is unproductive anyway, better to re-compile and see if I have fixed the first few and then attack the next.  So I don't accumulate big line changes.  Also languages like Python only give you one error at a time.

And I find most of my errors are ytpos so fixing them doesn't change the lines at all.

So I have never felt the need for this, and I fear its likely to add significant overhead to all users editing but only be useful to a few, which is not a good outcome.  Also it is likely to have many tricky corner cases.  

So my 2c would be "not a good idea" for the reasons above, but YMMV.

-- 
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-298137434
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20170428/b1ed0251/attachment.html>