Open colelawrence opened 2 years ago
Hi @colelawrence ,
I like the idea, but I wonder if this should be tied to the Separators, or any symbol (method, class, interface, etc) in the file.
I mean, Separators supports a set of symbols (methods, classes, interfaces, etc), but not all that you see in VS Code like variables. And you can disable Separators on globally and per-language, which means that in this case, the move up / down wouldn’t move to that disable Symbol.
So, do you need something tied to Separators itself or the Symbols presents in your file?
I'm interested in it being tied to separators themselves, so it's a visual cue. I would anticipate that having the separators visible makes predicting where the cursor will go much easier.
Thanks for clarifying
This is just an idea.
I'm thinking about additional ways to navigate my editor, and I was thinking it might be nice to use
CMD + Up
/CMD + Down
(which currently go to beginning of file and end of file) to actually jump to the separator above or separator below.If no separator is found above, then the beginning of the file.
If no separator is found below, then the end of the file.
A key to this experience that I like is that it corresponds to what separators are actually rendered, so it becomes a visual way to know where you're jumping to.