wojciech-kulik
commented
1 day ago Hi,
There are two types of errors:
- Errors detected by LSP and LSP can detect errors only in open buffers (not sure if only in visible ones). Those errors will be highlighted in a source code without building. You can also browse them using any plugin that supports it like
:Telescope diagnostics,:Trouble diagnostics. You can also use a built-in mechanism::lua vim.diagnostic.setqflist()to see them on quickfix list. - There are build errors that you can get from build logs and they will be detected in the whole source code (but keep in mind that sometimes an error in one place causes that the other place won't be built, so you won't see next errors until you fix the first one). When you build the project, the plugin parses errors and puts them in a quickfix list, so that you can navigate between errors across the whole source code. You can see those errors using
:Telescope quickfix,:Trouble quickfixor built-in:cl.
If your logs are missing file, that's either because it's some global error and there is no file in logs or it's a bug in parser and it's unable to detect the filename. You can post this part of original logs (your proj/.nvim/xcodebuild/original_logs.txt) with the error + your summary and I will check what's wrong.
John-Colvin
The xcode "Issue navigator" pre-emptively finds problems in the whole project - without me manually running a build - then lets me click on one of those problems and get taken to the relevant line & column.
My current experience using xcodebuild.nvim is that I can trigger a build, I get the error logs, but a) the summary shows a line number but not the file the error came from (it is visible above, but it does make the summary a bit useless) & b) I can't trivially "go to error location".
Note, I am not a neovim wizard yet, perhaps this is just in the category of "learn to write your own lua code to implement whatever you want", but perhaps I'm just missing some config.