Closed ErwinTATP closed 2 months ago
Please, wait until people who use Windows can help you...
@ErwinTATP, try to add the location of your Rterm.exe
also to the system path (for example: "C:\Program Files\R\R-4.2.2\bin\x64"). I think the path doesn't walk through subdirectories to find the rterm.exe. In my case it solved the issue, and I could make R run.
The plugin still complained that it couldn't find R or the neovim window at the startup, but it worked properly anyways, at least until now.
@jalvesaq Thank you for your great work!!
@JacintoCunha seems to be working so far, thanks!
I have several deadlines to catch up, so a complete test have to wait.
@ErwinTATP Is everything working okay? @jalvesaq please feel free to tag me in Window's issues...sometimes life gets busy and I might not visit the repo for weeks a time but I'm always willing to swing by to see if I can help somebody out with getting setup on Windows!
@akthe-at Sorry for not updating the issue progress for a while! So far everything seems to be working by adding Rterm.exe
location into PATH
, though it still seems to pop up tons of "can't find this, can't find that" now and then.
I'm closing this now.
I installed the plugin to work with NvChad, but when I open an R file, it reads:
When I went on to try to start R program (
\rf
), the R window opened for less than half a second, and then instantly closed. The following message appeared in the status bar:So I thought if the
nvimcom
package is correctly installed, so I ran:RDebugInfo
, the following reading appears: (I have no idea how to copy these messages I'm noob) Does this mean the package has been installed?I tried to add
R_path
in the systemPATH
andinit.lua
, but the error messages remain.Then I tried to edit
R_path
inconfig.lua
; this time, theR_path
andRterm.exe
messages disappeared, but it still said"Neovim" window not found
. I tried\aa
and\l
, but it only returned a messageDid you start R?
. I would highly appreciate some help.Additional info: I'm using Windows 11, and the neovim is run in CMD. I also tried Powershell, but that did not work either.