Page 1 of 1

start command conflict - Windows vs MSys

Posted: Thu 19 Oct, 2017 09:41
by kamil
Ever since I installed MSys, and it has a script that is called start, I can no longer use my F2-v menu shortcut to launch Visual Studio's shell:
start %comspec% /k ""C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\VsDevCmd.bat""

Now whenever I press F2-v, I get a Windows pop-up "Choose the program you want to use to open this file / File: start"

Any ideas how to fix it, so I could have both MSys and my F2-v working from within Far?

start command conflict - Windows vs MSys

Posted: Thu 19 Oct, 2017 10:21
by DrKnS
Add %comspec% /c to the front of your command or add start to system.executor.excludecmds in far:config.

start command conflict - Windows vs MSys

Posted: Thu 19 Oct, 2017 16:43
by kamil
thank you - that's very helpful.

%comspec% /c works just fine for me.
but just out of curiosity, how do I open/edit far:config?

start command conflict - Windows vs MSys

Posted: Thu 19 Oct, 2017 16:58
by HaRT
kamil wrote:
Thu 19 Oct, 2017 16:43
how do I open/edit far:config?
Just run far:config from the FAR command line.

start command conflict - Windows vs MSys

Posted: Thu 19 Oct, 2017 17:51
by kamil
thank you.

but I don't see system.executor.excludecmds there.

Image

start command conflict - Windows vs MSys

Posted: Thu 19 Oct, 2017 18:15
by John Doe

start command conflict - Windows vs MSys

Posted: Thu 19 Oct, 2017 18:37
by HaRT
kamil wrote:
Thu 19 Oct, 2017 17:51
I don't see system.executor.excludecmds there
Use menu filtering: Press CtrlAltF then type exclude.

start command conflict - Windows vs MSys

Posted: Thu 19 Oct, 2017 20:21
by kamil
HaRT wrote:
Thu 19 Oct, 2017 18:37
kamil wrote:
Thu 19 Oct, 2017 17:51
I don't see system.executor.excludecmds there
Use menu filtering: Press CtrlAltF then type exclude.
great - thanks