Skye Bender-deMoll

thanks! I'll try that. Perhaps a longer-term solution would be to ask @jjallaire to add a function like `newPlatformDevice()` to the rstudioapi, that would call whatever `plot.new()` would normally call....

BTW, I now see a new argument to `dev.new(noRStudioGD = TRUE)` added in R 3.1.1. it works on Windows, just not on unix systems (creates pdf instead of interactive x11...

No console errors for me. I just switched back from Patchwork to Oasis with the intention of testing the rebuild index PR ... and somehow this time the re-index was...

sorry I didn't get a chance to test this before https://github.com/fraction/oasis/pull/540 merge. Today I switched from patchwork, saw the problem, pull master and was eventually able to see and use...

... also discovered that I'm seeing different versions of oasis when I start via `oasis` vs `npm start` in my oasis dir (the later runs the master branch) I'm assuming...

seems like a bug in the CRAN link parser, but maybe putting line 496 and 497 on the same line would help it recognize that it is inside the \deqn...

is this an issue with ndtv's rendering or the network.plot functions?

ah ha! thank you! this probably explains #29 , which I haven't been otherwise able to reproduce. Were you also seeing the error message from MDSJ layout?

I have not tried inside a shiny app, but the ndtv-d3 vignette has an example of rendering a static network that can still be interacted with in the browser without...

fixing this will require a bit of refactoring in how ndtv looks up and locates user-added layout functions. As a work around, have you tried just adding Depends ndtv in...