-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
1.74 Intentionally Breaks Monkeypatch + CustomizeUI #1390
Comments
I really hope this project pushes back on PRs like the one causing this issue. It shows an egregious disregard for the community as a whole. |
We might disable the mangle since it also breaking the build process on Windows... I have to think about that. |
@daiyam that would be wonderful. thanks for taking a look |
@daiyam yes, please do. Thanks. |
OK, I've removed the mangle in the latest Insiders version. Can you test it? |
I will be able to test this evening |
Monkey Patch and / or Customize UI do not appear to function with this release. If there is an area that I can provide logs from to help the team please let me know and I'll be happy to share. Thanks! |
Ya, it seems that Monkey Patch hasn't been updated since it's impossible to maintain for the official version due to the mangling (iocave/customize-ui#156). |
Great news! I used the You can download the extension here: To install, simply run the command: Enjoy! |
Ya, the git is 2 weeks old while the extension is 3 months old (on VSMarket), 9 months old (on OpenVSX)... |
It shows after started:
Then I click "Install and Reload", it shows up still. |
@weaming check your extensions. If you don't see |
I reinstall them from vsix file (monkey patch) and MS market (custom UI), but my settings seem do not work as expect as before in VSCode. Expect: |
have you re-applied "Enable Monkey Patch" ?? |
It works after re-applied, tks! |
vscode@1.76 not work |
@zwmmm it works solely on vscodium |
it seems that there have been no updates for the extensions and VSCodium have been updated to the latest: 1.77.1.23095 |
Ah good, I thought it was just me. It's stopped working on v1.77 for me as well. I had to disable it to get going and had planned to investigate later, thinking I had accidentally changed something to break it. |
That's exactly why i had to post that "post" to let everyone know what's going on with the extension and the latest version. I am glad that you know you are not alone. |
I've fixed this bug in lehni/customize-ui@215ea7f and you can download a new version of the extension to install from a VSIX file here: iocave/customize-ui#170 (comment) Enjoy! |
@lehni If you generate a release in github, users could use VSIX Manager with the following settings to install and keep it up to date.
|
they did it again |
I will look into it when fixing the patchs for the insiders version |
Will the patch work with 1.79? |
if you are talking about VSCodium, then yes. and i am also using v1.80... it's working fine. Both monkeypatch + CustomizeUI will not work on VSCode. |
Many thanks, it's working..!! |
@Kaku-dev see here for a more future-proof way forward: drcika/apc-extension#52 (comment) |
Has anyone manage to get this running in the 1.83 release? |
@wtf403 Yes. Check out apc-extension |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment! |
This issue has been closed due to inactivity, and will not be monitored. If this is a bug and you can reproduce this issue, please open a new issue. |
Use Zed. Free yourself from the tyranny. |
Describe the bug
A microsoft employee merged a build change that effectively targets and breaks Monkeypatch and CustomizeUI. See: microsoft/vscode#166126. This was a purposeful and malicious commit to further control users of the app.
Please confirm that this problem is VSCodium-specific
Please confirm that the issue/resolution isn't already documented
To Reproduce
Steps to reproduce the behavior:
code --verbose
from the terminal, or try to start VSCodium from the applications menuExpected behavior
I was half expecting the project not to pick up malicious changes from MS like this. But it's understandable that this went under the radar.
I would love to see this change excluded, as I view this kind of this as harmful as the telemetry.
Screenshots
n/a
Desktop (please complete the following information):
Additional context
Here's the stack that code produces, which is identical to the stack that vscodium produces:
The text was updated successfully, but these errors were encountered: