Alexandru Dima
Alexandru Dima
Blame points to https://github.com/microsoft/vscode/compare/15415b6de68f3fcfefcd264ac37cc3c3d54a378b...a1842c8f633237d6d850ada5772359ad32480655 I think it could be https://github.com/microsoft/vscode/commit/5f75c4a41091ac36faea06bf86965d507ce77fa8
View zones added to the original editor do not render when the diff editor is configured to be rendered inline. But view zones added to the modified editor will render...
> View zones added to the original editor do not render when the diff editor is configured to be rendered inline. But view zones added to the modified editor will...
That is currently not possible. It is not possible to insert a view zone inside a deleted zone of text when the diff editor is rendered inline.
We do security patch releases only in case we become aware of a vulnerability that affects VS Code. We are tracking all CVEs issued for all of our dependencies, including...
The go to error widget does two things: 1) inserts a view zone to reserve a vertical gap in the text 2) inserts an overlay widget that is kept position-wise...
Monarch was contributed initially by Daan Leijen and I am just maintaining it at this point, but it looks like our yaml Monarch parser manages to overcome the indentation change...
@Tronic I also maintain `vscode-textmate`, which is the TextMate grammar engine that executes in VS Code and I'm not 100% sure, what has TextMate recently added that is now used...
The problem here is that there is an assumption that the visible ranges and the selection must change atomically, but that's not the case. For us, first the selection moves...
That's a good idea! PR welcome!