-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does {startup} work with positron? #136
Comments
I'm not a user of Positron. Does the ordinary |
Yes, the ordinary
|
That's all the output?
It clearly finds the folder and it identifies 11 files there-in. |
You can also try to call startup::startup(debug = TRUE from the Positron prompt and see what you get. If you get an error, what does |
The VSCode output is an example of {startup} working as expected, in contrast to the output from Positron which doesn't seem to find the Manually running Here are the full logs from Positron
|
…on and Rprofile files have been skipped [#136]
I think I've identified the reason, and it has to do with Positron launching R using:
Specifically,
That tells |
I'll try that out. I also updated to the dev version of {startup} asI saw you made some commits and get this error:
|
Oops - forgot to add some new files to repo. |
Nice, things seem to be working now, thanks! |
The startup package doesn't seem to work with position. I use {startup} with VSC all the time without issue, however it doesn't work in positron (not even if I trigger it manually with
startup::startup()
). I wonder if this could be related to ark?The text was updated successfully, but these errors were encountered: