Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Use env extension when available#24564

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
karthiknadig merged 14 commits intomainfromenv-ext1
Dec 10, 2024
Merged

Use env extension when available#24564

karthiknadig merged 14 commits intomainfromenv-ext1
Dec 10, 2024

Conversation

karthiknadig
Copy link
Member

No description provided.

@karthiknadigkarthiknadig added the feature-requestRequest for new features or functionality labelDec 9, 2024
@karthiknadigkarthiknadig added this to theJanuary 2025 milestoneDec 9, 2024
@karthiknadigkarthiknadig self-assigned thisDec 9, 2024
@karthiknadigkarthiknadig marked this pull request as ready for reviewDecember 10, 2024 06:21
hideFromUser: this.options?.hideFromUser,
});
} else {
this.terminalShellType = this.terminalHelper.identifyTerminalShell(this.terminal);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

this isn't 100% accurate in terms of always getting the shell type right, correct?

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

It is not, this is the same detector as the one Python extension uses. We need the shell type API to be more accurate.

});
this.terminalAutoActivator.disableAutoActivation(this.terminal);

await sleep(100);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

is there reason why we wait for short duration before activateEnvironmentInTerminal

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This is also from the existing activation. This is to give shell initialization enough time to start.


if (pythonEnv && project) {
const fixedOptions = options ? { ...options } : { cwd: project.uri };
const terminal = await api.createTerminal(pythonEnv, fixedOptions);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

it seems like this is calling createTerminal from env extension API, Im trying to understand why this and the interpreter one are both called "legacy"

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Because it is temporary solution to the old features in the Python extension. These apis can be deleted when we delete the code for old Python features.

@karthiknadigkarthiknadig merged commite789348 intomainDec 10, 2024
99 checks passed
@karthiknadigkarthiknadig deleted the env-ext1 branchDecember 10, 2024 08:25
@karthiknadigkarthiknadig added verifiedVerification succeeded and removed verifiedVerification succeeded labelsJan 27, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@anthonykim1anthonykim1anthonykim1 approved these changes

@eleanorjboydeleanorjboydAwaiting requested review from eleanorjboyd

Assignees

@karthiknadigkarthiknadig

Labels
feature-requestRequest for new features or functionality
Projects
None yet
Milestone
January 2025
Development

Successfully merging this pull request may close these issues.

2 participants
@karthiknadig@anthonykim1

[8]ページ先頭

©2009-2025 Movatter.jp