>
> match-brackets does work on [], and {} as well. What kind of syntax
> regards "//" as bracket markers?.
>
Oh, really? Didnt know that. And thus never used it in this way. Well, it's
wonderful. But...
Do you know that if you have construction like `text(brackets{curly})` -
the actual selection will depend on where your cursor is standing?
Say you'rу on letter 'r' of 'bracket' - the (...) would be selected. Say
you're on 'e' - {...}.
Why? Because, that's why.
And next - why WITH brackets? I dont want them, all my use cases do not
want them to be selected. That's why actually I never use it - cause it
selects also brackets. This is not what I expect command to do (compare
with vim's `ci(`). This looks like if ctrl-w would select word WITH
surrounding spaces. Who wants that?
And again. I miss not only __select the inner area__. I generally miss
__move to the closest symbol (maybe even closing bracket)__. Selecting area
surrounded by brackets is practically useless feature.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/CAC%2B8SVyVv%2BAMq%3D%3D-XDEFDW0RW5-ZJn3enM1-3gwPGXOeZX_G2A%40mail.gmail.com.
