-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command line Options reference? #123
Comments
Hi @speedmind. TE3 does not support the command line syntax yet. There will be a separate .exe for use with the command line, with a much smaller footprint than the current TE3 executable (this is mentioned on the roadmap as "Standalone CLI application"). For the time being, please use TE2 for any command line requirements, as it is fully compatible with the file formats used by TE3. |
Hi @otykier and thanks for the prompt response. Sorry I missed the CLI reference in the roadmap. Thx again, |
Hi @otykier I've a similar Issue with TE2. I've a C# script that works ok using the GUI but I'm not be able to execute it using this power shell script:
Can you help me? |
I'm considering the use of TE3 for a project, but so far I've not been able to use the same features from a command line as for TE2 as described in the documentation Command line Options.
I'm using the portable version of TE3 but so far I've not been able to invoke it using a similar approach to TE2:
start /wait TabularEditor.exe /?
or
$p = Start-Process -filePath TabularEditor.exe -Wait -NoNewWindow -PassThru -ArgumentList "/?"
Both methods (command line & PowerShell) throw an Unexpected exception upon GUI startup, which is not the expected behavior.
I've also looked in the roadmap for TE3 and I've not seen anything regarding command line options.
So the ultimate question is. Is this a bug with the current release (latest as of now using 3.0.7 with trial license) or just something that's not enabled in TE3? If it's the latter can this aspect be added to the roadmap?
Thx in advance,
Vas.
The text was updated successfully, but these errors were encountered: