-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smart identation, keywords. #135
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, I tried to use vim plugin and founded, that usefull information is lost with compression.
Here is some structure block in file:
vscode minimap:
code-minimap with compression 1:1
compression: H:0.25; V:0.5
really - this block not recognizable, and this kills 90% of minimap sense I think.
Block is worser and worser recognizable with more compression.
I suggest smart identiation blocks rendering.
Try to add block start on first place of block start
and block end on last place of block end.
I mean
start:
End:
Also first / second level identation should have fixed shift, not depending on compression. As example 2 dots, not one or zero.
here is one as example, and it's not recognizable.
The aim is to quickly recognize first / second identation level structures / functions / classes / functions, defined in classes.
Does it possible to remove newlines between blocks? (suppose that not?).
Also probably it's would be good to add some marks by keywords?
As example: shift all output on one symbol. And use free column for marks.
We pass some dictionary to program: {'class': 'c', 'function': 'f'}, e.t.c.
And you add this marks at first free column.
Probably some patterns for structures ? like
{'{' : "\w+ = {", '}': "}"}
Also it would be good to add some custom symbols for fixed line numbers.
Smth like
{bookmark_glyph: [129, 160, 569], breakpoint_glyph: [69, 129, 489]
where bookmark_glyph, breakpoint_glyph are utf-8 font glyphs
And you added this glyphs for specifief lines numbers, not compressiong them.
The text was updated successfully, but these errors were encountered: