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

2017-04-25 Thread Vasiliy Faronov
This is my naive attempt at solving #1136. It works for me (not heavily tested yet), but I’m not sure if it’s a good idea. I would appreciate any feedback. Geany’s message window is sort of detached from the editor. In general, it’s just lines of text that are not parsed or associated with the f

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

2017-04-25 Thread Vasiliy Faronov
@vfaronov pushed 1 commit. ef3702c Forget line shifts in message window on document (re)load -- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/geany/geany/pull/1481/files/dfb12b9dfa33b18bf19cc98f7310c0f1a123a9b0..ef3702cde4cc2b7c3c8f74ab

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

2017-04-28 Thread 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

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

2017-04-29 Thread 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 a

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

2017-04-29 Thread elextr
@vfaronov I admit my Python is mostly small changes to a large application, or test harnesses for the C++. So I don't use much in the way of Python-Ninja tools :) I think Scintilla has a way of adding per-line data, maybe that will help, though it may be only for lexers, not sure. Certainly i

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

2017-04-29 Thread elextr
Also corner case questions, what do you do if the line the message references is deleted, or combined with another line or moved to a totally different place in the file? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: http

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

2017-05-08 Thread Vasiliy Faronov
> Certainly if the change is simple and the overhead is small then its a more > attractive change. No, unfortunately, that change would be more complex, although its runtime overhead would be smaller. Given the lack of interest in this issue, it does seem that brittle or complex solutions are

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

2017-05-08 Thread Vasiliy Faronov
Closed #1481. -- 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#event-1072342003