Solidify ChimeraX app name on Windows

[Zach Pearson]

In our last developer meeting we discussed the name of ChimeraX on Windows and the implications of taking the .exe off of the name or not, but overall the goal was to open a ticket and take it off the meeting agenda. I'm not up to speed on the nuances of the Windows platform, so I'll probably take a backseat in this discussion.

[Greg Couch]

So this is not about removing the .exe. It is about have the console version be called ChimeraX.exe instead of ChimeraX-console.exe. That way users on all platforms would use "chimerax" as the binary (Linux because it is a symbolic link, Man and Windows because they are case-independent file systems). If using a terminal window, the short name is much easier to use. And if using the GUI, typically via the Start menu, the actual filename is never seen. For comparison, Python uses python.exe for the console app, and pythonw.exe for the GUI version. See ​https://stackoverflow.com/questions/9705982/pythonw-exe-or-python-exe for a discussion of the differences.

We can make the change anytime, but I wasn't planning to do it until the nogui interface is worked on. That way we'll be able to tout the improvements and document the name change at the time.

[Eric Pettersen]

I'm beginning to lean towards Greg's position. I've already had to explain on the list once to use chimerax-console.exe to run a script since chimerax.exe produces no message on stdout even in nogui mode.

[Eric Pettersen]

If we do this, we should probably leave chimerax-console.exe as a link to chimerax.exe, so that third-party scripts don't break.