You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a feeling this must be a Linux-only bug that noone's reported since noone is using this on Linux.
Could I confirm from a Mac user that this isn't seen on your machine?
opening a R/markdown file works fine
using the "Open file" navigation menu displays no files, and the filepath dropdown is empty (and cannot be typed into)
clicking the up arrow errors out the entire Shiny app session
The stack trace points to mod.editr (a function for the packager I put together changing a couple parameters to editr) — I've replicated the issue when just using the plain editr function.
The inner end of the stack trace points to fileGet at line 54 which appears to be from shinyFiles
Save works (and is even tied to Ctrl + S)
Happy to be assigned to fix this, just can't figure out precisely what's going wrong at the minute. (A variable "hidden" stores a list of shinyFilesButtons,
At a guess it seems the problem might be coming from shinyFiles:::shinyFilesButton('open') — so I might be best raising an issue on that repo instead?
The text was updated successfully, but these errors were encountered:
I have a feeling this must be a Linux-only bug that noone's reported since noone is using this on Linux.
Could I confirm from a Mac user that this isn't seen on your machine?
The stack trace points to
mod.editr
(a function for the packager I put together changing a couple parameters toeditr
) — I've replicated the issue when just using the plaineditr
function.The inner end of the stack trace points to fileGet at line 54 which appears to be from
shinyFiles
Ctrl
+S
)Happy to be assigned to fix this, just can't figure out precisely what's going wrong at the minute. (A variable "
hidden
" stores a list ofshinyFilesButton
s,At a guess it seems the problem might be coming from
shinyFiles:::shinyFilesButton('open')
— so I might be best raising an issue on that repo instead?The text was updated successfully, but these errors were encountered: