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

Backing to depricated option to Integrated Terminal #305

Merged
merged 1 commit into from
May 7, 2022
Merged

Backing to depricated option to Integrated Terminal #305

merged 1 commit into from
May 7, 2022

Conversation

felipemarkson
Copy link
Contributor

@felipemarkson felipemarkson commented Apr 13, 2022

The solution for Integrated Terminal doesn't work anymore.

More details of the problem in: #288

@flathubbot
Copy link
Contributor

Started test build 86198

@flathubbot
Copy link
Contributor

Build 86198 successful
To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/84043/com.visualstudio.code.flatpakref

@nedrichards nedrichards merged commit 95b6d50 into flathub:master May 7, 2022
@felipemarkson felipemarkson deleted the patch-1 branch May 7, 2022 15:19
@nikodunk
Copy link
Contributor

nikodunk commented May 7, 2022

@nedrichards FYI with #309 the non-depricated option for the integrated terminal works great for me too. Are we sure we want to suggest the depricated option by default again?

@Nightfirecat
Copy link

Nightfirecat commented May 7, 2022

I can confirm as of cfc88be I was using the recommended terminal setup prior to this change without issue, since #309 was merged--it was working fine. This PR suggests using a deprecated method for setting the terminal which should be avoided. I strongly recommend reverting this merge.

@nikodunk
Copy link
Contributor

nikodunk commented May 7, 2022

Agreed. @barthalion @nedrichards can we revert this merge? There's already so much confusion out there as to whether the terminal works on VSCode Flatpak or not - recommending a deprecated solution is not going to help our cause.

@nedrichards
Copy link
Member

I'll take a closer look. It's not ideal for sure.

@nikodunk
Copy link
Contributor

nikodunk commented May 9, 2022

Would it be helpful to open a PR to update to the current syntax for settings.json as we had before?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants