WrapEarnPass left a comment (geany/geany-plugins#1577) I am annoyed with the output from on-before-save and on-save not recognizing file output specification (file:line:col), so I dropped back to Geany:Build to see how it deals with it.
<img width="889" height="303" alt="Image" src="https://github.com/user-attachments/assets/1a95d07e-0934-4fba-a82d-bf1eafa66e2d"; /> Simply, it seems. Explode on \n. If the message starts with \w+:\d+:\d+, that's a filespec. This leads to messages getting broken up into seemingly unrelated "lines" in the view, but allows for line jumps almost every time. It doesn't even test for the trailing colon <img width="633" height="343" alt="Image" src="https://github.com/user-attachments/assets/d07b7439-b506-4761-a08a-755ac7bf85c3"; /> It doesn't test for full paths either. testfilea.c:1:1 will jump to the most recently edited loaded file named testfilea.c, if there are multiple open. This does not seem like a high bar to clear, so Auto-run should format output from stdout or stderr to match Build. Break on newline. Jump to most recently edited file matching filename.type:line:col Nice to have, maybe glue records between filespecs into a single message? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1577#issuecomment-4798696932 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany-plugins/issues/1577/[email protected]>
