Closed jeroldhaas closed 7 years ago
So, in short, grab VS 2017 RC and check if the bug is gone.
Wow. Ok, Vasily. Thanks.
@vasily-kirichenko Perhaps there are some drink(s) we could buy you to make one service release for VS2015 at some point? :) :) Just wondering if it might help the community grow in the enterprise situations where they will no doubt be stuck on VS2015 for a while :)
@dsyme that's a bug in VFT, not in VFPT, as I said. We don't touch brace matching at all.
@dsyme that's a bug in VFT, not in VFPT, as I said. We don't touch brace matching at all.
Yep, understood. I just wanted to raise the prospect of a service release at some point :) Though fundamentally the convergence with VFT is awesome :)
:) The last VFPT release was long time ago and no serious bugs have been found so far. So, if there are bugs, I'll certainly fix them.
@ReedCopsey was calling out to release a new version with latest FSharpXaml to avoid issues for end-users:
@smoothdeveloper somehow I forget about it :( It's just released.
Description
When using VsVim to edit a
.fs
or.fsx
file, highlighting of matching braces doesn't work. Disabling VsVim restores the behavior. Other file types work with matching brace / parenthesis highlighting.Repro steps
Please provide the steps required to reproduce the problem
.fs
or.fsx
file with matching parentheses / braces or write code with them therein.Expected behavior
Braces & parentheses (
(
,)
,[
,]
,{
,}
) should show matching character.Actual behavior
Placing the caret over one of the "supported" characters yields no highlight for the matching character.
Known workarounds
Current workaround is to disable VsVim, which removes all vim-style editing capabilities.
Related information