Skip to content
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

Epic: Private Beta #2239

Closed
7 tasks done
petetronic opened this issue Feb 12, 2024 · 6 comments
Closed
7 tasks done

Epic: Private Beta #2239

petetronic opened this issue Feb 12, 2024 · 6 comments
Labels
area: builds Issues related to Builds category. epic Epic
Milestone

Comments

@petetronic
Copy link
Collaborator

petetronic commented Feb 12, 2024

@petetronic petetronic added this to the Private Beta 2024 Q1 milestone Feb 12, 2024
@petetronic petetronic added the epic Epic label Feb 12, 2024
@wesm wesm added area: builds Issues related to Builds category. and removed epic Epic labels Feb 29, 2024
@petetronic petetronic added the epic Epic label Feb 29, 2024
@jennybc
Copy link
Member

jennybc commented Mar 1, 2024

Observations on Home > Machine Prerequisites > R Prerequisites

  • I would be tempted to mention rig. Because, for most R folks, one of the cool things about Positron is that it becomes much more feasible to have and regularly use more than 1 version of R. And rig is definitely the easiest way to do that.

    Possible wording: "To install R, follow the instructions .... Alternatively, if you'd like to have multiple R installations, rig is a great way to manage this and Positron plays well with this set-up."

  • Have we recorded why we need dev cli and dev crayon? To the extent that it has anything to do with usethis, early next week I will merge Use cli r-lib/usethis#1956. So if the recommendation stems from usethis, we could recommend installing dev usethis and not mention dev cli or crayon.

  • Recommend dev usethis, regardless.

  • In general, tidyverse and r-lib show dev installation via pak::pak() these days in their READMEs and pkgdown sites, so I suspect we should do that here as well. (Especially since positron-r uses pak!)

@jennybc
Copy link
Member

jennybc commented Mar 1, 2024

Observations on Interpreter Selection > Choose a new interpreter:

The warning about losing state ... presumably this is a bit more subtle for R? We do have a setting for restoring .RData:

Screenshot 2024-03-01 at 1 38 53 PM

which reminds me that #964 is still open re: hitching this up with behaviour around saving .RData.

In any case, it's a big deal for R users that, by default at least, we absolutely opt them in to the "blank slate" lifestyle. This is going to surprise some folks (but I think it's super healthy and I'm so glad we're doing it).

@jennybc
Copy link
Member

jennybc commented Mar 1, 2024

Observations on Troubleshooting > Python and R Logs > Output Panel

Positron R Extension is another biggie to mention. That is, for example, where the test explorer logs.

@jennybc
Copy link
Member

jennybc commented Mar 1, 2024

Observations on Updating Positron > Via Update Script.

Maybe we should have a clickable hyperlink to the update script, so someone could easily read it before they take the leap of faith by downloading and running it.

@juliasilge
Copy link
Contributor

I believe the need for dev cli and crayon is not very driven by usethis. Here is an example of what we need these dev packages for.

@juliasilge
Copy link
Contributor

With the work done in #2494, we now consider the "writing code" part of this finished. ✅

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: builds Issues related to Builds category. epic Epic
Projects
None yet
Development

No branches or pull requests

4 participants