Nikolaus Huber (Oct 23 2026 at 10:14): Nikolaus Huber (Oct 23 2026 at 10:14):Hej!
I've been using isabelle vscode for a while, and generally really enjoy working with it. It took a while to fully configure it so that the difference between the version shipped with Isabelle and my "normal" VSCode isn't so noticeable, but one thing I just cannot get to work reliably is the git plugin, that already comes pre-installed with isabelle vscode. It seems to work ok most of the time, but then occasionally it will mark a full file as having changed, even though only a couple lines were altered, and most of the time, when I'm double checking the diff before committing it shows files as completely blank, even though there is definitely code in them. The same happens if I try to resolve a merge conflict with the inbuilt merge editor, most of the time I just get three empty editor panels. Is somebody else having similar issues?
Fabian Huch (Oct 23 2026 at 11:30):This sounds like a problem of the git plugin, although perhaps the problem won't be visible in the next release (or current devel version) of Isabelle/VSCode.
Nikolaus Huber (Oct 23 2026 at 11:31):I would assume that the git plugin is the same as the one used in regular VSCode, right?
Fabian Huch (Oct 23 2026 at 12:17):Yes.
Fabian Huch (Oct 23 2026 at 12:23):Until recently we had a problem in the LSP where unnecessary (but idempotent) full-file edits were sent, and given that VSCode used to have tons of problems with filesystem operations, I would speculate that the git plugin does not handle this well.
Last updated: Oct 25 2026 at 22:21 UTC