Comment 17 for bug 1659172

Explanation of inkscape.com vs. inkscape.exe:
On Windows you can have either console applications or GUI applications. Console applications don't have a window but can easily output text to the console. GUI applications do have a window but can not easily write output to the console.

To work around this issue we build two executables:
- inkscape.exe is the actual Inkscape application and is compiled as a GUI application (using GCCs "-mwindows" linker flag).
- inkscape.com is a wrapper that is compiled as a console application (using GCCs "-mconsole" linker flag). It only sets up console input/output and links it to a newly spawned instance of inkscape.exe.

In other words: If you run inkscape.com you'll always end up with a child process of inkscape.exe. Running inkscape.exe directly will only create one process.

When running "inkscape" (without extension) Windows will pick the first executable matching this file name when omitting the file extension and therefore will always launch inkscape.com (as it's first alphabetically).