Add (hidden?) option to disable ctrl+click link functionality

[GoogleCodeExporter]

I find that, due to the layout of my laptop, and my constant use of screen in 
ssh sessions, I'm frequently accidentally ctrl+clicking on the mintty window.  
I've tried adjusting the settings on my laptop's touchpad, but it just doesn't 
provide a good enough "palm oops" detection to avoid this.

Since I pretty much never use the ctrl+click function, it would be helpful for 
me to have a way to disable the ctrl+click function.  For as often as I use it, 
the select+right click+open path is fine for me.

Since this probably isn't a feature tons of people want, it seems reasonable to 
make this a setting in minttyrc, but not exposed in the options window, if 
you'd rather do it that way.

Original issue reported on code.google.com by fastcat@gmail.com on 21 Sep 2010 at 5:03

[GoogleCodeExporter]

What's the make of the laptop (so I can try to avoid it)? ;)

And how do you manage to do anything on it considering that accidental clicks 
without modifier must be much more frequent than Ctrl+clicks, thus activating 
windows and pressing buttons you didn't mean to?

I'm not at all keen on adding a mintty-specific workaround for what's a 
system-wide design flaw. Can't you address this with Autohotkey or some such?

Original comment by andy.koppe on 21 Sep 2010 at 8:46

[GoogleCodeExporter]

Actually, accidental clicks without a modifier aren't a problem for me.  Some 
of it is how the palm check feature works: it disables the touchpad for an 
adjustable period of time after you do any typing.  Modifier keys don't count 
there, though.  Some of it is also mechanical: the physical motions of sending 
some of the ctrl+a,ctrl+whatever sequences to screen causes my palm to hit the 
touchpad considerably more often than it does with normal typing.

It does look like Autohotkey could be used to steal the control click from 
mintty and send it to the bit bucket, and I understand the rationale for not 
wanting to add a feature to mintty based solely on reasons like this.  On the 
other hand, installing a second program to remove a feature from the first also 
feels a bit ... icky.

Original comment by fastcat@gmail.com on 21 Sep 2010 at 9:27

[GoogleCodeExporter]

Having mulled over this a bit, I decided not to implement the option, for the 
moment anyway. That's for the aforementioned reason that it's a system-wide 
problem that seems to be fairly infrequent and that there are other 
workarounds. I'd still be interested to see what type of touchpad has this 
issue though.

What I have done is to stop mintty from trying to open an empty filename, i.e. 
you'll no longer get the "cannot find the file specified" box if you Ctrl+click 
in empty space. That should make the problem a bit less frequent at least.

Original comment by andy.koppe on 25 Sep 2010 at 5:11

• Changed state: Rejected

[GoogleCodeExporter]

Since I don't tend to leave the mouse cursor over text (generally want to read 
text :), having it ignore ctrl+click on empty space I think will actually fix 
>90% of the problem for me, thank you :)

Original comment by fastcat@gmail.com on 4 Oct 2010 at 9:16

[GoogleCodeExporter]

I know this an old issue which was rejected, but I find the ctrl-click feature 
is *constantly* bringing up the "The system cannot find the file specified" 
warnings.

I'm using mintty under Cygwin with a Dell Precision M3800, with "tap-to-click" 
enabled.

The point about why this is not an issue with regular clicks is well taken.  In 
my use of mintty, such clicks don't result in anything happening.  But if I for 
instance plan to click control and some other key, and my trackpad registers a 
tap (== click) , I get the warning - sometimes several others as well.

I never use ctrl-click.  To get around this, I've had to disable tap-to-click, 
which is a bit of a loss for me as I know need to reach further across a large 
touchpad to click.

Original comment by terry.m...@gmail.com on 25 Jul 2015 at 3:15