I see we now use the editor font in the "Find References" tree:

First of all, if we start to use this we should also use it in the search results view to be consistent (the results already look very similar).
I suggest to have a setting for this though, I prefer the workbench font for search results in lists like that.
//cc @Microsoft/vscode for more UX input
Agree for consistency and search.
What is a bit visually jarring to me here is a combination of fonts used in the find all references tree (I understand this is the only logical way to do it)

Yeah, it is a little ugly
I love it. Code type should be monospace; otherwise it shouldn't.
This is the right way to go.
First of all, if we start to use this we should also use it in the search results view to be consistent (the results already look very similar).
Yep, we should fix every spot where we render code and use a non-monospace font.
Yep, we should fix every spot where we render code and use a non-monospace font.
Need to be careful though, monospace text is a lot wider and the viewlet is typically very narrow. Doing this may have a usability impact on smaller screens.
To me it looks like a bug when we show code in the editor/monospace font but it is not colorized.
Most helpful comment
To me it looks like a bug when we show code in the editor/monospace font but it is not colorized.