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
using Geany with R and compiled code #2532
Comments
If you compile C in a separate shell there is nothing Geany can do, if you compile it in Geany the compiler errors should be parsed and linked to the source line of the error. Rists are welcome to upgrade the wiki article as required. |
@elextr Thanks for feedback. I tried to use command I seen during my compilation:
and it looks to work
The thing is that I am not getting real-time response about errors. |
Correct. Geany only reports errors given to it by the compiler when the compiler is executed. It doesn't do like some IDEs where they highlight errors/warnings in real-time as you type. |
@codebrainz Thank you. Any idea if there is any plugin that would allow that? or maybe an existing feature request for such functionality, so I can subscribe and be informed if such functionality will be available? |
@jangorecki I'm not aware of any current ones. I had previously tried using libclang for C/C++ but ran into some issues integrating it as a plugin (mentioned in #1195). There is also some discussion #1458. |
Many R packages contains compiled code, most commonly C.
I found some docs about using Geany with R https://wiki.geany.org/howtos/using_geany_with_r but they not mention anything about compiling C code.
Could anyone extend documentation on how to setup Geany for R's compiled code? I can imagine this is probably
R CMD SHLIB
command somewhere there.Presently on the line.
I am getting
Not sure if that matters, but strictly speaking I am interested in C code being highlighted when there are compiler warning/error, so I can spot errors as I type. I do compilation of a package in a separate shell session.
Thank you.
The text was updated successfully, but these errors were encountered: