Double-click selection selects first word of next line
When double-click dragging to select text, if you drag past the last character of a line, it will include the following line-break; any leading whitespaces; and the first word of the next line…
I haven't been using Rider for that long, so I don't know if this is the normal/expected behavior across all the different IDEA applications… But it goes against how pretty much all other applications handles double-click selection.
Is there a way to make Rider stop selecting the next line?
Hopefully I just have to check or uncheck a checkbox somewhere, but I can't find it.
(I have verified that this behavior is the same in both Windows and Linux)
(it will also keep selecting “next word” forever if you move the cursor onto the sidebar or beyond, this part seems like a bug though)
Please sign in to leave a comment.
Hi Philip,
I reproduced the behavior and submitted two new bug reports for it:
While #2 is definitely a bug, #1 may actually be a feature. I've seen comments in other related tickets on YouTrack where people actually preferred this behavior. Let's wait for a word from developers about it.
Thanks!
Thank you,
Yeah, I think you're probably right.
I just personally can't see why anyone would want to include the next word...
Or rather, why anyone would EXPECT it to be included without having to mouse over it.
But I can definitely imagine that some people might want to include the whitespaces before it.
(just not me, I would expect the selection to stop at just before the line-break)
Hopefully a developer will come back with the reasoning for it as well, if it is actually supposed to work like this.
Anyway, having options for it would definitely be appreciated, even if it is only in the registry.
I am here because I also thought this was a bug.
I think the reasoning for it might be that the user can stop moving the mouse in the last half of the last word to avoid the behaviour if it isn't wanted. Which is great until every “last word” is a semicolon. Good luck hitting the last half of that.
Hi Jbloodthorn, both bug reports are still open. Please consider following them to receive notifications of any progress.