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

Terminal profile settings are not respected when launching scripts #21960

Closed
ghost opened this issue Sep 11, 2023 · 4 comments
Closed

Terminal profile settings are not respected when launching scripts #21960

ghost opened this issue Sep 11, 2023 · 4 comments
Assignees
Labels
triage-needed Needs assignment to the proper sub-team

Comments

@ghost
Copy link

ghost commented Sep 11, 2023

Type: Bug

Behaviour

Expected vs. Actual

Expected:
Pressing F10 to run any Python file in an integrated Terminal while respecting the Terminal profile settings defined in the terminal.integrated.profiles.linux

Actual:
Newly created Terminal does not respect the settings defined in the terminal.integrated.profiles.linux

Steps to reproduce:

  1. Define any settings in terminal.integrated.profiles.linux, I have the following:
"fish": {
            "path": "fish",
            "env": {
                "fish_history": ""
            }
        }
  1. Open up any .py file and press F10 to run
  2. Observe if the env settings took effect

Diagnostic data

  • Python version (& distribution if applicable, e.g. Anaconda): 3.10.12
  • Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Poetry
  • Value of the python.languageServer setting: Default
Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings


languageServer: "Pylance"

testing
• unittestEnabled: true

Extension version: 2023.17.12541009
VS Code version: Code 1.82.0 (8b617bd08fd9e3fc94d14adb8d358b56e3f72314, 2023-09-06T22:07:18.759Z)
OS version: Linux x64 6.2.0-32-generic
Modes:

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Sep 11, 2023
@karrtikr
Copy link

Please provide the debug logs which can help diagnose the issue:

  • Run Developer: Set log level command
  • Select Python -> Select Trace
  • Run Developer: Reload Window command
  • Provide the output:
Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

XXX

@github-actions github-actions bot added the info-needed Issue requires more information from poster label Sep 11, 2023
@ghost

This comment was marked as resolved.

@github-actions github-actions bot removed the info-needed Issue requires more information from poster label Sep 12, 2023
@karrtikr
Copy link

Thanks, I'm able to reproduce the issue. This actually seems like an issue on VS Code itself, I'll open one for you and link it here.

@karrtikr
Copy link

Closing in favor of microsoft/vscode#192943.

@karrtikr karrtikr closed this as not planned Won't fix, can't repro, duplicate, stale Sep 12, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

1 participant