I think supporting one additional selection delimiter configuration apart from word-wise but less than line wise, would make sense, but going beyond that I think, this would probably make things less usable for the user, as in: they might be getting confused by how many clicks they did and end up redoing the click-sequence again, just to get what they want.

So,

• single click: starts linear selection
• double click: selects word wise selection
• if configured: one click more will select an extended word wise selection
• one click more (3 or 4 times therefore) would do line wise selection

Going for more than one extra layer is certainly possible but I don't see how that could improve workflow. Users should probably be using vim-mode and motion sequences to quickly select a range).

That's just a thought so far.

So now, how would one configure it. Probably with an optional configuration key per profile that would have a name, something like, alternate_word_selection_delimiters or so, that accepts a string of all characters that are allowed to be part of such a word. (just like we have already, but for the alternate word selection, which can be triggered using 3-click).

I would disagree with the assumption that users would be confused. I agree it's a novel selection mode and therefore shouldn't be the default, but what OP described/requests here is very precisely what I believe is the most useful selection behavior for programmers / tech savvy folks, in a terminal, when using the mouse.

This is because in general, I always want to select things on a word boundary, but because I deal with various technical things and not English literature, the delimiters in question will be different from one time to another. Therefore no amount of devising the best heuristic will work. Just give me a mode that expands the selection to one more delimiter at a time, even if that means more clicks, and even if that means an arbitrary large amount of clicks might be necessary to reach the full line.

I hope I correctly rephrased OP's FR. I can relate — the status quo of mouse text selection in terminals is extremely frustrating today.

Thanks for this! Though now I have one extra level it really convinces me I wan't multiple :-)

e.g.http://[fd12:1:0:8:0:1:c0a8:4d69]/

For word selection in e.g. yaml files, : is in word_delimiters so the first double click in the IP gets just one 16 bit value. I have [] in extended_word_delimiters so another click and I get the IP, but one more and I get the line rather than the URL which would be want I would really like.

Thanks for this! Though now I have one extra level it really convinces me I wan't multiple :-)

e.g.http://[fd12:1:0:8:0:1:c0a8:4d69]/

For word selection in e.g. yaml files, : is in word_delimiters so the first double click in the IP gets just one 16 bit value. I have [] in extended_word_delimiters so another click and I get the IP, but one more and I get the line rather than the URL which would be want I would really like.

I see, I think that instead of adding another click during selection we can add user defined selection by delimiter, so you can add something like

    - { mods: [Control],        mouse: Left,        action: Select, chars: ' ' }

So during C+left click on the url it will select everything between spaces
what do you think about it?