Improve naming of "editor.minimap.mode" setting and its values

[weinand]

Testing #91250:

When reading the following in my settings file, I have no idea what this means:

"editor.minimap.mode": "actual",

And I have a hard time understanding what the other two "modes" "contain" and "cover" really mean.

So I tried hard to understand what is controlled by the "mode". On a mathematical level it is a "projection", but this is not something to "throw" at users.

On a simpler level it is the "size" of the minimap.

Based on this we could rename "mode" to "size" and use these values and descriptions:

• "sameSize": Minimap has the same size as the editor contents (and might scroll).
• "shrink": The minimap will shrink as necessary to never be larger than the editor (no scrolling).
• "shrinkOrExpand": The minimap will stretch or shrink as necessary to fill the height of the editor (no scrolling).

[alexdima]

	actual	contain	cover
small
large
current	minimap.mode: actual	minimap.mode: contain	minimap.mode: cover
opt1	minimap.size: sameSize	minimap.size: shrink	minimap.size: shrinkOrExpand
opt2	minimap.height: proportional	minimap.height: fit	minimap.height: fill

[alexdima]

We decided in the standup to go with minimap.size and the values proportional, fit and fill.

[gjsjohnmurray]

We decided in the standup to go with minimap.size and the values proportional, fit and fill.

Is it too late to lobby for this to be changed to minimap.height rather than minimap.size? Reason being, I'd like to request a future enhancement that'd allow me to set a maximum pixel width for the minimap. On wide screens the way the minimap width increases proportionally to the display width of the file means it can become unnecessarily wide.

Narrow:

Wide:

Seems to me that the left-side portion of the minimap is often sufficient to give me a sense of where I need to scroll to.

[gjsjohnmurray]

Nevermind. I've just noticed editor.minimap.maxColumn already exists.

With "editor.minimap.maxColumn": 30 my wide screen layout becomes: