I’d also want a command for key binding.

@seanmcbreen

• Adding a toggle that writes to user settings and enables/disables the minimap for all editors is easy. Such a toggle fits in with our settings story.
• Adding a toggle that enables/disables the minimap for the current file (similar to toggle word wrap) is ridiculous hard due to our settings story, which does not have this concept. For the toggle word wrap we need to maintain an in-memory file-based dictionary and work around the entire workbench settings story. We need to spy on when the workbench applies the settings coming in from our configuration service, and immediately undo the incoming settings, such that we establish the desirable toggle in all cases. Here are some of the ridiculous high amount of bugs that we had when the toggle tried to use the settings story. And here is the controller that constantly spies on all editors to undo the incoming settings. I suggest we plan for this and involve @sandy081 and @bpasero such that the configuration service is enhanced with per-file settings such that I don't need to write another one of those for the next file-level toggle we want to have.

Which type of toggle do you have in mind when you say "We should add a toggle"

Adding a toggle that enables/disables the minimap for the current file (similar to toggle word wrap) is ridiculous hard due to our settings story, which does not have this concept

Such an oversight, considering that vim has had set vs setl for ages.

I went with the easy implementation that writes to user settings.