> Therefore, eslint error messages (correct) lead to wrong column. This will be true with most tools, even e.g. GCC. Fortunately, if you run those tool from inside Geany (as a build command), support for extracting the offset on the line uses character? code point? anyway, it "just works" for most people currently. So if you called eslint that way, it would probably work.
IMO the issue here is "invalid" as we do display the visual column (not character count) which is what was intended, yet indeed somebody could add a new placeholder for the byte/code point/glyph to fit specific needs. Note the complexity/irrelevance of some of those depending on various factors highlighted e.g. in #745 (encodings, glyph vs. code point, etc.). -- 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/issues/2733#issuecomment-765995583
