I just turned off the "minimap" feature of #VSCode after realizing I've had it on for like a decade without ever looking at it. Is it useful somehow, or just a gimmick?
@scanton Yeah, all my recent work on building a language server has had me discover a ton of nice features, like searching for symbols with Cmd + T. We'll see about hiding the sidebar entirely... perhaps one day :)
@jgillich Yeah, but apparently not neat enough for me to ever look at it 😄 OTOH I haven't been bothered by it either, until just today when I needed to split the editor across a couple of files and it suddenly was very much in the way.
I always thought it was an interesting idea to have an overview of the code. You can presumably see classes etc as things indent and unindent. Or the big blocks of doc strings. Which could give some landmarks.
But I work on too much code that's just a set of functions, and I don't know the layout of my code, so I guess "that's the big long function" never helped for navigation.
@ibboard@jgillich yeah, it feels like something that can easily be motivated as potentially helpful, because we really want it to be… not because we were ever helped by that.
@anderseknert@jgillich Or it's old and outdated. I'm thinking of all of the C code (?) that has huge "region" blocks as comment directives so that you can skip over that group.
Maybe it's useful for that kind of structure, where files are huge but explicitly structured for legacy "our search isn't good enough and we've got outdated code review practices" reasons. Possibly with an intention of printing it (which was in the coding standards of a company that I joined in 2006!)
@ohmrun Yeah, but even without the minimap, there'll be a red rectangle next to the scrollbar at the position of the error.. or at least as far as I can see?
Add comment