[Feature Request] Enable cli to use allready open instance of fork (single instance)

[felixhirt]

It would be awesome if i could tell fork from the cli to open a given repo in the allready open instance (or start up, if fork.exe is not allready running), something like fork.exe --singleInst "path/to/my/repo"

[felixhirt]

This could also be used as ground work for #89

[felixhirt]

Just a quick follow up: Was this implemented wIth the release of 1.37? And if so, is there a doc for the cli arguments?

[DanPristupov]

No, sorry. I'll do my best to introduce it in 1.38.

The task is 50% done, but not everything works properly yet.

This feature seems to be trivial, but it requires IPC communication which is always difficult and error prone.

[felixhirt]

Thanks for the quick response and all the work you put into fork. I only asked because it is still in the 1.37 milestone, no problem if it takes longer.
PS: I agree, IPC is hard, especially if you dont control the rest of the environment

[DanPristupov]

I'm uploading 1.38 update right now. It will handle CLI requests in the active instance (if it exists).

[felixhirt]

Thanks a lot. Is there a documentation somewhere for the cli arguments possible? i tried fork -help and fork /?. I can open a second instance with "fork" or just focus the current instance with "fork --singleinst", but i cannot open a repo in the current instance

[DanPristupov]

Currently the only option is the repository path.

examples:
fork .
fork c:\path\to\repo

It should find an active instance (or create a new one if none were found) and handle the request in it.

I think second instance should never be opened (if you are using Fork higher than 1.38 version, of course). Does this really happen?

[lnist]

From PowerShell C:\Users\<my.user>\AppData\Local\Fork\Fork.exe $pwd works and opens in already open instance, but C:\Users\<my.user>\AppData\Local\Fork\Fork.exe . only focuses the open instance.

[DanPristupov]

It looks like the working directory path is incorrect when command is called from Powershell. So, relative paths don't work, however absolute paths must be handled properly.

At the time I'm trying to figure out why Fork gets a wrong working directory.