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

We MUST maintain a fork #2030

Open
ismailarilik opened this issue Sep 15, 2024 · 2 comments
Open

We MUST maintain a fork #2030

ismailarilik opened this issue Sep 15, 2024 · 2 comments

Comments

@ismailarilik
Copy link

The context: microsoft/vscode#519 (comment)

Microsoft is not interested to fix long-awaited vscode issues. So why don't we fix them here? I know it is a big burden but I think we need to try.

@daiyam
Copy link
Member

daiyam commented Sep 15, 2024

Oh, I was wondering how to change that. No wonder I didn't find out...

I'm maintaining VSCodium.
But I use MrCode which is my fork of VSCodium with some fixes (primarily fix for the tab character in the terminal). It's been 3 years that I tried to push the fix the xterm.js (a MS project). So I know that MS can be frustrating.

VSCodium don't usually accept new feature.
But it's such a basic feature that I will accept a PR for the Insiders version.

@ismailarilik
Copy link
Author

This isn't a simple change. This is why Microsoft doesn't wanna try to fix it. If you see the attached PR on the upstream issue, you can see that more than 80 files need to change.

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

No branches or pull requests

2 participants