Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why won TextPipe run from the command line?

April 26, 2017Command line run textpipe

0

Posted

Why won TextPipe run from the command line?

1 Answer

0

Posted

(Try using the Command line wizard in the Tools menu) There are a number of possible answers. Firstly, the evaluation edition of TextPipe always displays a dialog when it runs that requires operator intervention. This dialog is not in the registered versions. Secondly, you may not have specified /G /Q at the end of the command line. This tells TextPipe to run the current filter and exit when it has finished e.g. “C:\Program Files\DataMystic\TextPipe\textpipe.exe” /f=autorun.fll /g /q Thirdly, you may have forgotten to correctly quote long filenames (e.g. those with spaces). You must use double quotes around the ENTIRE parameter. e.g. “C:\Program Files\DataMystic\TextPipe\textpipe.exe” “/f=long filename filter.fll” /g /q See the notes in TextPipe’s help file under the command line topic.