Citation leads to RStudio freeze #709
-
When I try to cite something my RStudio session becomes unusable. In particular, if I add a citation like [@example1900] and then remove the brackets (@example1900), I get this "Working..." message on top and cannot click any button. I run an Archlinux based OS, so not sure if it is the reason for this bug and maybe everything is perfect on Mac and Win. |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 8 replies
-
One thing that might help is to export a request log to see exactly where things are getting hung up (info on doing that here: https://support.rstudio.com/hc/en-us/articles/200488538-How-To-Export-a-Network-Request-Log-From-the-RStudio-IDE) |
Beta Was this translation helpful? Give feedback.
-
There was a hunspell problem at first, I added .aff, .dic files, but still getting an error.
|
Beta Was this translation helpful? Give feedback.
-
It looks to me like RStudio is looking for version of Pandoc that doesn't exist (at Net: this is some sort of misconfiguration or environment conflict which is incredibly hard to debug speculatively. |
Beta Was this translation helpful? Give feedback.
-
Makes me think that there could be an Arch packaging issue related to a change we recently made (which was in fact moving |
Beta Was this translation helpful? Give feedback.
-
@jjallaire I don't think this is a Arch related issue. I updated RStudio and Quarto in my Ubuntu machine
and I'm having he same issue. I have
in RStudio log. I checked the |
Beta Was this translation helpful? Give feedback.
-
Right Pandoc is in |
Beta Was this translation helpful? Give feedback.
-
Yes, you are right, the release just came out today (I thought it was already out!). |
Beta Was this translation helpful? Give feedback.
It looks to me like RStudio is looking for version of Pandoc that doesn't exist (at
/home/dat/pandoc
). I'm not sure why this would be -- do you have anRSTUDIO_PANDOC
environment variable set? You might want to try removing that file to see if it clears things up.Net: this is some sort of misconfiguration or environment conflict which is incredibly hard to debug speculatively.