Nope but that’s not an atom error, that’s an error with the elixir build. It happens in other cases as well. A quick google search:
https://github.com/BlakeWilliams/Elixir-Slack/issues/130
Among others.
The gist of it though seems to imply that either your current compile is corrupt, or you have beam files currently in your project that were compiled with a different OTP version (did you just upgrade OTP and did not delete your _build directories in all your projects?). But it is an error with mix building things, not atom, atom is only reporting what mix reports it (the elixir integration runs an elixir daemon to query the elixir system directly).
But yes, actually you can hack to make clicks keybindable, but that involves doing some Is magic on atom’s internals 
With “normal” keybindings you can’t mess with mouse in any way.
