You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting up extraterm from a binary zip download and passing in some flags and options (e.g. --cygwinDir) doesn't parse the options correctly.
The problem is in the commander module which Extraterm uses to parse command line arguments. It assumes that the first two items in process.argv are the nodejs executable and then the name of script being executed. This assumption is violated when starting up the packaged version of Extraterm.
A workaround is to pass an extra dummy value before the first flag or option. i.e. extraterm.exe XXX --cygwinDir c:/foo
The text was updated successfully, but these errors were encountered:
sedwards2009
changed the title
Start up options and flags don't work correctly from the zip binaries
Command line start up options and flags don't work correctly from the packaged binaries
Mar 23, 2016
I would assume this is a quick fix? I would love to see a universal solution that not only works with Electron but in general. You mention in #512 having two parse functions. I would like to give that a +1.
Starting up extraterm from a binary zip download and passing in some flags and options (e.g.
--cygwinDir
) doesn't parse the options correctly.The problem is in the
commander
module which Extraterm uses to parse command line arguments. It assumes that the first two items inprocess.argv
are the nodejs executable and then the name of script being executed. This assumption is violated when starting up the packaged version of Extraterm.A workaround is to pass an extra dummy value before the first flag or option. i.e.
extraterm.exe XXX --cygwinDir c:/foo
The text was updated successfully, but these errors were encountered: