Skip to content

"Activate Python Environment in Terminal created using the Extension" triggering on all terminals #20754

Description

The setting above (ID python.terminal.activateEnvironment) seems to be applying to all terminals, even ones not created by the extension.

Activity

  1. karrtikr commented on Feb 27, 2023

    @karrtikr

    That's how that setting is currently intended to work, as it is how many of our Python users expect it. Is there any issue you're having with it?

  2. karrtikr commented on Feb 27, 2023

    @karrtikr

    Soon we'll be using #11039 to do it implicitly and stop sending commands to terminal, which may solve your issue.

  3. asportnoy commented on Feb 27, 2023

    @asportnoy
    Author

    It sends a command to the start of each terminal which is a bit annoying. The language of the setting says it'll only apply to terminals created using the extension, so if that's not the case, the language should be updated.

  4. karrtikr commented on Mar 2, 2023

    @karrtikr

    Sure, we can update the language.

    It sends a command to the start of each terminal which is a bit annoying.

    We'll stop doing that with #11039.

  5. added
    debtCode quality issues
    needs PRReady to be worked on
    and removed
    triage-neededNeeds assignment to the proper sub-team
    on Mar 2, 2023
  6. asportnoy commented on Mar 2, 2023

    @asportnoy
    Author

    Thank you! ❤️

  7. karrtikr commented on Mar 2, 2023

    @karrtikr

    Welcome!

  8. locked as resolved and limited conversation to collaborators on Apr 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions