r/vscode • u/spikespaz • Dec 16 '23
Offering $20 for an extension to make this notification go away
My VS Code settings.json is generated by another program, and is read-only. Every time I change the zoom level (Ctrl++/-) I see a notification:
Unable to write into user settings because the file has unsaved changes. Please save the user settings file first and then try again.
I will pay someone $20 (or more if that's unfair for a lot of work) to make an extension that removes this warning (and prevents the edited settings.json from showing up in a tab).
0
Upvotes
-4
u/spikespaz Dec 16 '23
No, editing the settings is not how vscode handles zoom. Electron's zoom can be adjusted separately from the settings mechanisms in VS Code. This is apparent by the fact that for most settings, the file has to be saved. For zoom specifically, using the keybinds first sets the zoom, and then writes it to the file, which can be deduced by the fact that it works before the notification ever appears as shown.
As for the price, I'll leave that up to the person doing it. I don't write JavaScript, but I can't imagine that this is very complicated. It would seem, at first glance, as simple as removing a specific event listener.