fsharp
fsharp copied to clipboard
dotnet
Disappearing lines when editing the same file in multiple document tabs
This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work] When editing a code file (in this case F#), with the same file open in multiple document tabs, the edited line occasionally just disappears in one of the tabs. The code is still present and can be seen in the other tabs, but the text is not visible and the line not visibly editable in that one tab, but it will accept and process input, again visible in the other tabs. Also, a blank space the height of another line appears above it, as if from CodeLens (with no line number next to it), but CodeLens is disabled.
The affected tab is most commonly, but not always, the one that's being edited.
I have not used Visual Studio 2022 before 17.1, so I cannot say whether this issue occurred in earlier versions. It has never occurred in prior major releases of Visual Studio.
Original Comments
Feedback Bot on 2/20/2022, 10:25 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Original Solutions
(no solutions)
I'd be surprised if this is F# specific, would be good to have a specific repro. Another bug did mention disappearing lines though this time the mention of multiple tabs may be key
@dsyme @vzarytovskii so after spending 30mins trying to reproduce this, I am fairly sure this is actually related to F# CodeLens, and only in the "above the line" mode. You don't even need multiple tabs for that :D
https://user-images.githubusercontent.com/5451366/194320035-264f3eda-20a8-4568-a440-0119b5bfeae2.mp4
FYI I was just trying to type this:
let test1 = 42
let test2 = 42
This is as miserable as it can get - but I think CodeLens is generally not working in the "above the line" mode so if we decide to remove that mode altogether this will also go.
Anyway, will put it on my CodeLens radar.
For now, closing this as a duplicate of #12625
Please reopen it if you can reproduce it without CodeLens involved.