"Working directory" discrepancy with the two ways for launching Hyper

• I am on the latest Hyper.app version

• I have searched the issues of this repo and believe that this is not a duplicate

• OS version and name: Windows 10 Pro x64

• Hyper.app version: 2.0.4

• Link of a Gist with the contents of your .hyper.js: n/a

• Relevant information from devtools (CMD+ALT+I on Mac OS, CTRL+SHIFT+I elsewhere): n/a

• The issue is reproducible in vanilla Hyper.app: Is Vanilla

Issue

Please note: while this may not necessarily be a direct duplicate of another issue, it is possibly related to a number of them (#2343, #2214, etc..).

While tweaking a few things in my environment, I set GitKraken to use Hyper instead of Windows cmd, but in doing so I noticed something interesting.

I first tried using the version-agnostic executable path %LOCALAPPDATA%\hyper\Hyper.exe, but passing a directory path to this executable doesn't seem to work.

Changing the path to %LOCALAPPDATA%\hyper\app-2.0.4\Hyper.exe instead seems to work fine.

I've confirmed the same behaviour with each executable from Windows cmd, where I also noticed that the exe that is not in the app-2.0.4 folder launches Hyper in a separate thread, while the one in the app version folder shows runtime logging output in the command prompt window I launch it from.

These discrepancies make it difficult to efficiently integrate this terminal with other dev tools in the Windows environment... So it would be nice to get both of them to work the same way if possible. :)

Reproduce the discrepancy from Windows cmd using %LOCALAPPDATA%\hyper\Hyper.exe and the app-2.0.4\Hyper.exe path, passing a directory to each. Compare their working-directory behavior and command-prompt output; done means both launch methods behave consistently when integrating Hyper with GitKraken or other Windows tools.