Enable Triple-Click Line Selections (disable training wheels)

[BusyConcept]

I read the note about Triple-Click Line Selection being disabled due to their "accidental nature". I'm not sure what kind of unskilled coders you know, but I don't know any coder who needs these kind of training wheels on a Text Editor. Seriously, if someone needs to be protected from using a triple-click line select, they should probably find a new profession/hobby. No other developer who has forked this project is doing this. Please reverse this change.

[ProgerXP]

I'm not sure what kind of unskilled coders you know

Yours truly. I sometimes find myself doing another click when I think the first didn't register, and I realize it did only after I've pressed the button for the 3rd time. This is frustrating and similar to how we've disabled Alt (#399) - when you "speculatively" think in advance and that action turns out to be unnecessary but undoing its effect is tedious.

Just checking, you know that clicking on the gutter as well as Ctrl+Shift+Space (if you prefer the keyboard) does the same thing, right? Unlike the triple click (which I do use in other apps), they don't have the problem I describe.

Are you a user of Notepad 2e specifically?

Related: #313

[dg-wfk]

Ok, I understand both of your sides. But what I do not understand is, why not make it optional. I mean, that is exactly the reason why there is a "Settings" menu and an .ini file with 506 (minus section headers) lines of options. We would not need any settings at all, if all users agreed to what is useful for them and what is not. And you ProgerXP added even some settings (i.e. keyboard language in window title). So why did you decide not to simply enable or disable those features, but made them optional?

[ProgerXP]

But what I do not understand is, why not make it optional.

Because this feature requires patching Scintilla sources and I try to limit this as much as possible for easier future migration. You can check https://github.com/ProgerXP/Notepad2e/blob/master/doc/Scintilla_ChangeLog.md to realize how many patches there are already. Pushing setting-specific logic there would make the patch bigger (whether it'd be critical or not is up to debate but it'd be bigger, it's a fact).