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 RTags with Tramp #1240
Comments
is the directory where rdm resides on remote machine added to tramp-remote-path variable? Please see #546 for background. |
Yes, as I mentioned above, I installed rtags on the remote machine and added the path to tramp-remote-path variable |
I've reincarnated the environment, run rdm successfully. also compilation indexed the project (I'm using wrapper shell script to index it), but when trying to browse the remote code I'm experiencing problem around please let me know how far You did go |
Hi,
However, I still cannot browse through my code. I tried using rtags-find-symbol or rtags-find-references, I just get "RTags: No results" |
did You pass any arguments to rdm binary during startup ( If please try to issue any looking at
|
Tried this again and it works without any issues. Thanks! |
Is your feature request related to a problem? Please describe.
My code is on a remote VM and all the development happens on that machine. I currently ssh into the machine and open up emacs and use RTags. RTags does not work if I open the project using TRAMP.
Describe the solution you'd like
I would like to use RTags in the above-mentioned scenario. I tried setting rtags-tramp-enabled and adding the path to my tramp-remote-path. However, I get an error saying that the server cannot be started.
Additional context
I looked into the code a bit.
rtags-executable-find
returns just the executable name if tramp is enabled here . However, when starting the server - inrtags-start-server-unless-running
the check fails hereUnfortunately, I don't have significant knowledge of elisp. If someone can guide me a bit around this, I can write the fixes for this.
Thanks,
Tapan
The text was updated successfully, but these errors were encountered: