Repository navigation
Enhancement: Minimap position highlight #21404
Description
- VSCode Version: 1.10.0-insiders (2017-02-24)
- OS Version: Windows 10
I have some enhancement requests for the current minimap implementation which are already available in Atom as separate plugins.
- 1. Enable the minimap in latest insider build and position your cursor in the editor. The minimap does not highlight (ligh grey background) your current position unless you hover over the minimap. I would like this highlight to be enabled at all time.
- Implemented via issue Minimap: add a
alwaysShowViewportsetting #21784. A new flag was added"editor.minimap.showSlider": "always"(its default is however set tomouseover)
- Implemented via issue Minimap: add a
- 2. Add CSS color display in the minimap, this is available in
Atomas a separate pluginminimap-pigmentswhich I find very convenient. - 3. Highlight the text in the editor would also highlight the text in the minimap. This is only available in
Sublime Textand has a white background (instead of grey)... see print screen.- see this comment
Activity
mika76 commentedon Feb 25, 2017
I think 3 is the one I mostly use - so easy to find or find and replace when you can see the highlights in the minimap - as long as they are very visible (strong contrast) - in atom and sublime the highlights are not nearly as visible as they should be, it's too easy to miss them in the syntax colors...
sillero commentedon Mar 1, 2017
if minimap is enabled AND with the behavior fixed as Ghislain B. (@ghiscoding) suggested, we don't need that slim default bar, minimap replaces it
rmunn commentedon Mar 9, 2017
Request 1 (always show the viewport on the minimap) is now being tracked at #21784. Request 3 seems to be a partial duplicate of #20934 ("editor selection" is one of the things asked for in that issue). Request 2 does not have any duplicates that I could find.
jens1o commentedon Mar 14, 2017
I would like it when the current line is also highlighted in the minimap.
globaltommy commentedon Mar 28, 2017
I'm very surprised there is no highlight on minimap - guess will STILL stick with atom.io for now.
abhijitvalluri commentedon Apr 3, 2017
Request 3 is a feature that exists in Atom, at least via third-party packages. In my opinion, that is very much needed and without that the utility of the minimap is questionable at best. Hopefully they will implement this feature soon.
In the meantime, I'll still be sticking with VScode instead of atom as I totally love the git integration in VScode, including the diff feature and due to the search feature being in the sidebar rather than editor window.
abhijitvalluri commentedon Apr 15, 2017
I quickly hacked together a rudimentary implementation of Request 1 and 3 at abhijitvalluri@a1f2d2f
For request 3, I couldn't yet figure out how to highlight just the precise token corresponding to the word that is highlighted. So, instead I decided to highlight the entire line. In my opinion, this is probably a bit better as it is easier to see the whole line light up instead of just the word, which will be much smaller and harder to spot.
Example screenshot:
You could take that code, modify it and make your own custom version of vscode. And if you can make it nicer still go ahead and send in a PR!
abhijitvalluri commentedon Apr 17, 2017
Made some improvements to the minimap highlight implementation: https://github.com/abhijitvalluri/vscode/commits/minimap_enhancements
Right now, all the implementation details are hardcoded, including it being set up for a dark theme. Also, there is a bug wherein if the file is too large, so that the minimap scrolls and does not fit entirely in one view, then only highlights for the portion of the file that is visible in the minimap works. Once you scroll, there are no highlights for the invisible part of the file in the minimap.
UPDATE:
I have made the necessary changes to fix the issues I mentioned above: highlights work correctly even for very long files, scrolling does not remove highlights etc. in abhijitvalluri@46c6691
If you don't mind this hardcoded feature, and are fine with the dark theme, then you can make a packaged version of this by running:
And then you will have your very own vscode with highlighting in the minimap. This is good enough for me, for now! So I am using this as my default version of vscode! 🤓
ghiscoding commentedon Apr 17, 2017
alexandrudima do you think it would be possible to use/merge the code provided by Abhijit Kiran Valluri (@abhijitvalluri) for the number 3. that I have in the list
abhijitvalluri commentedon Apr 17, 2017
My code may not be in a good shape for merging. So, I can clean it up if needed so that these changes can be made use of in vscode! Do let me know.
ghiscoding commentedon Jun 8, 2017
The number (1) from the list has now been implemented Minimap: add a
alwaysShowViewportsetting - 21784. A new setting will available in the June version."editor.minimap.showSlider": "always"37 remaining items
dcastil commentedon Jun 11, 2019
I'd like to see the minimap have all the highlighting features of the scrollbar to replace the scrollbar completely. It feels strange and unnecessary to have two scrollbars for the same window.
ghiscoding commentedon Jun 11, 2019
I've added a comment in next June 2019 Iteration Plan, you guys can up vote there as well if you wish.
MatrosSkin commentedon Jun 11, 2019
Here is a link to comment to vote: #75103 (comment)
mirineumark commentedon Jul 5, 2019
So....The new version came out. It....sort of has this feature we have been waiting for for 2.5 years. A couple problems:
It only highlights in the minimap if you search the page. Double-clicking on things that highlights other instances of it on the page does not do anything in the minimap.
The highlight is so tiny and subtle it might as well not have been added. Its supposed to highlight in a way that is clear and obvious and instead its so hard to see that in the documentation they had to add a circle around the part of the minimap so people would be able to tell it was there at all.
Any chance these can be fixed in less time than 2.5 years? These seem like pretty simple changes to make.
ghiscoding commentedon Jul 9, 2019
Our wishes might have been heard...
that was pulled from July Iteration Plan (2019), it does sound like this ticket 🤞
EDIT
Unfortunately, they are actually different issues with similar subject title. I'm afraid that our issue will not be addressed at this time. Sad to see that it takes years to look into this 😿
stiegi commentedon Aug 12, 2019
With the release of 1.37.0 we kind of have that feature now. The only downside is that it doesn't work on simple selections, but on searches only. That means you need to doubleclick first, and press CTRL+F afterwards... We are almost there. Is there a way to automate searching for the selection?
PierreMarchand20 commentedon Aug 12, 2019
I tried to talk about it in #78807 along another issue which is assigned to the person who implemented the feature for the search selection. Wait and see
RMacfarlane commentedon Aug 12, 2019
Hey all! I did the work on search results in the minimap, which was the first step of enabling decorations in the minimap. This was meant to be the foundation for further decoration improvements to the minimap. I'm not working on this in the current iteration, but this issue is on my radar!
ghiscoding commentedon Aug 12, 2019
Rachel Macfarlane (@RMacfarlane)
This is great news, thanks for the info. We waited 2.5 years, so I'm sure we could wait for another iteration before seeing it implemented. We just hope it will be this year lol
RMacfarlane commentedon Sep 11, 2019
I've just checked in the change for showing selection decorations in the minimap, it will be available in tomorrow's VSCode Insiders if you want to try it out early, otherwise in our next stable release in October.
ghiscoding commentedon Sep 11, 2019
Rachel Macfarlane (@RMacfarlane)
Thanks for the change, this is very welcome change on the productivity side.
Note that I proposed 3 enhancements and now 2/3 are done, we are still missing the "Show Color in Minimap" but it was not as high interested as the other 2 were. You close the issue but I wonder if that would be doable in the future? Should that be a separate issue?
RMacfarlane commentedon Sep 11, 2019
Ghislain B. (@ghiscoding) Can you open a separate issue to track that?