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.

Sign up for GitHub

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

Jump to bottom

Disable discovery or console for specific languages #3575

Closed
Tracked by #3541
, #1617
...
jthomasmock opened this issue Jun 18, 2024 · 3 comments
Closed
Tracked by #3541
, #1617
...

Disable discovery or console for specific languages #3575

jthomasmock opened this issue Jun 18, 2024 · 3 comments
Assignees
@jmcphers
Labels
area: core Issues related to Core category. area: runtimes Issues related to Language Runtimes enhancement New feature or request info needed Waiting on information
Milestone
2025.02.0 Pre-Rel...

Comments

@jthomasmock
Copy link
Contributor

While we very much want Positron to be multilingual, I know there will be teams that are only using a single language, such as R or Python. It may be useful to be able to turn off specific language auto-discovery, especially as the number of supported consoles grows over time.

I'll open a separate issue for inclusion/exclusion: #3574
@jthomasmock jthomasmock added the enhancement New feature or request label Jun 18, 2024
@juliasilge juliasilge added area: core Issues related to Core category. area: runtimes Issues related to Language Runtimes labels Jun 18, 2024
@jmcphers
Copy link
Collaborator

You can already do this at a user level by disabling the associated extension.

image

But agree it'd be useful for admins to be able to control this.

@jthomasmock jthomasmock mentioned this issue Jun 19, 2024
Closed
29 tasks
@petetronic petetronic added this to the Release Candidate milestone Jun 19, 2024
@sharon-wang sharon-wang mentioned this issue Jul 16, 2024
Open
@andrewheiss andrewheiss mentioned this issue Jul 16, 2024
Closed
@juliasilge juliasilge mentioned this issue Nov 14, 2024
Closed
@petetronic petetronic added the info needed Waiting on information label Jan 14, 2025
@petetronic
Copy link
Collaborator

We need to spec out the desired behavior here

@sharon-wang sharon-wang mentioned this issue Jan 15, 2025
Open
14 tasks
@jmcphers jmcphers self-assigned this Jan 28, 2025
@jmcphers jmcphers mentioned this issue Jan 28, 2025
Merged
jmcphers added a commit that referenced this issue Jan 30, 2025
@jmcphers @sharon-wang
Add option to control startup behavior per language (#6145)
5177ff7 
This change adds a new option that can be used to gain more control of
how Positron starts an interpreter for each language.

<img width="614" alt="image"
src="https://github.com/user-attachments/assets/cb609ebb-d170-4fda-95da-009d5cb07db4"
/>

The default value, _auto_, gives the automatic behavior we have today;
the others (enumerated in documentation elsewhere) are new behaviors.

In addition, this PR adds a new feature that allows a language pack to
tell Positron which runtime to start for a workspace _before_
discovering all the runtimes on the machine. This happens during the
_Starting_ phase of the startup lifecycle.

Addresses #3575.


### Release Notes

#### New Features

- New "startup behavior" option to control whether specific languages
will start a console in new Positron windows (#3575).

#### Bug Fixes

- N/A


### QA Notes

This new option replaces the old `interpreters.automaticStartup` option
(I think having both would be too confusing). If memory serves we're
using that today in the `qa-example-content` repro. PR updating this
option here: posit-dev/qa-example-content#44

As a debugging aid, I've added a way to show and clear which runtimes
are "affiliated" with the workspace. The new `Interpreter: Clear Saved
Interpreter` command can be used to show you which R/Python/etc.
versions Positron has saved as the ones for your workspace.

<img width="623" alt="image"
src="https://github.com/user-attachments/assets/dbd27b05-c914-4e4c-b759-13c2c45720e6"
/>

We will ultimately need more and better UI for choosing what interpreter
is associated with your project; this command should be seen as a
stopgap/debugging aid.

I've also added a couple of options to the Zed test language runtime so
that in a dev build you can try out the 'recommended for workspace'
workflow.

<img width="375" alt="image"
src="https://github.com/user-attachments/assets/5fca1868-cbb5-4ff8-a365-64f438ee333c"
/>

---------

Signed-off-by: Jonathan <[email protected]>
Co-authored-by: sharon <[email protected]>
@sharon-wang sharon-wang mentioned this issue Jan 31, 2025
Open
13 tasks
@testlabauto
Copy link
Contributor

Verified Fixed

Positron Version(s) : 2025.03.0-4
OS Version          : OSX

Test scenario(s)

Looks good with one caveat filed as a separate issue:
#6268

Link(s) to TestRail test cases run or created:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jmcphers jmcphers

Labels
area: core Issues related to Core category. area: runtimes Issues related to Language Runtimes enhancement New feature or request info needed Waiting on information
Projects
None yet
Milestone
2025.02.0 Pre-Release
Development

No branches or pull requests
5 participants
@jmcphers @petetronic @juliasilge @jthomasmock @testlabauto