-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to find location of errors #181
Comments
Hi, There are two types of errors:
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 ( |
See that the filename is there in the first print-out but not in the second. |
Ok, I know why it happens. This plugin does not support other files than |
Just a note, I checked recently if I could quickly add support for other extensions, but right now |
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.
The text was updated successfully, but these errors were encountered: