REditorSupport / sublime-ide-r

R-IDE: Make Sublime Text a perfect IDE for R
MIT License
113 stars 7 forks source link

R-IDE locks R Markdown files #6

Open lgaborini opened 6 years ago

lgaborini commented 6 years ago

It often happens that R-IDE spends too much time parsing .Rmd files in Sublime Text.
As a result, the files are locked for a good minute until the indexer fails, so I cannot perform any saving operation in RStudio.
E.g. write in Sublime Text, save, alt+tab to RStudio, run a chunk, perform small edits, save. This last step often fails due to locked files.
However, I can work and save in Sublime Text without problems, any time.

It happens even if the .Rmd file is NOT open in Sublime Text (but it lies in the indexing scope of the current project). The syntax highlighting is perfectly applied, but this issue forces me to completely close Sublime Text while using RStudio.

Here is what Sublime Text console prints once a .Rmd file is modified in RStudio:

reloading /C/Work/expertise/src/report_curves.Rmd
worker 12328 appears stuck while processing file /C/Work/expertise/src/report_curves.Rmd, killing process
indexing: crawler exited while processing /C/Work/expertise/src/report_curves.Rmd, no symbols recorded

(ok it is not very helpful, but I could not figure out how to increase the verbosity)

Sublime Text 3.1.1 3176 Latest R-IDE Windows 10 Insider 17738

randy3k commented 6 years ago

Thanks. It is not an issue of R-IDE though. You may want to see if SublimeTextIssues has a similar issue or report a new one.

lgaborini commented 6 years ago

If I disable R-IDE, the problem disappears, and I can work concurrently on Rmd files!

randy3k commented 6 years ago

Is it a problem for a specific Rmd file? Or all Rmd files suffer the same issue?

randy3k commented 6 years ago

Ya, I could reproduce it. Let me see if I could do anything.

randy3k commented 6 years ago

Thanks for the issue. It should be fixed by 53282c3. v0.1.4 is out.

lgaborini commented 6 years ago

Thank you, it is much better now.
Sometimes it still locks some files, but for less time. Also, the workers are no longer killed, but indexing completes successfully.