Felipe Monteiro de Carvalho:
> It does not split partially quoted arguments AFAIK
> Not sure about Free Pascal Trunk however.
>
> If FPC Trunk also does not support this, then I'm
> sure a patch to improve StringToPPChar would be
> welcome.
Version 2.4.4 does split, say
--name="Anton Shep
In our previous episode, Jonas Maebe said:
> >> output=outputfile.org','tempfile.wav']);
> >
> > While better, this is afaik not required per se, the executing
> > binary can
> > strip them also while doing cmdline parsing.
>
> I don't know any programs other than shells that would do so. FPC
On Fri, 9 Sep 2011, Marco van de Voort wrote:
In our previous episode, michael.vancann...@wisa.be said:
You must remove the quotes around 'outputfile.org':
Status:=ExecuteProcess('/path/to/oggenc',['-Q','--output=outputfile.org','tempfile.wav']);
While better, this is afaik not require
On Fri, Sep 9, 2011 at 1:46 PM, Anton Shepelev wrote:
> Is the parameter separation algorithm intentionally
> made to split partially quoted arguments like
> '--file="my file"'? If not, then, maybe the
> StringToPPChar() function should be fixed?
It does not split partially quote
On 09 Sep 2011, at 13:40, Marco van de Voort wrote:
In our previous episode, michael.vancann...@wisa.be said:
You must remove the quotes around 'outputfile.org':
Status:=ExecuteProcess('/path/to/oggenc',['-Q','--
output=outputfile.org','tempfile.wav']);
While better, this is afaik not re
On Fri, Sep 9, 2011 at 1:40 PM, Marco van de Voort wrote:
> While better, this is afaik not required per se, the executing binary can
> strip them also while doing cmdline parsing. It doesn't matter for
> executeprocess.
I wrote that section in the wiki when I had a real issue where the app
did
On Fri, September 9, 2011 13:40, Marco van de Voort wrote:
> In our previous episode, michael.vancann...@wisa.be said:
>>
>> You must remove the quotes around 'outputfile.org':
>>
>>
>> Status:=ExecuteProcess('/path/to/oggenc',['-Q','--output=outputfile.org','tempfile.wav']);
>
> While better, t
Marco van de Voort:
> It should now be possible to pass the parameters
> to tprocess separated. I don't remember if that
> change made it to 2.4.4 though, otherwise it will
> be in 2.6.0.
Thanks for letting me know.
Is the parameter separation algorithm intentionally
made to split par
In our previous episode, michael.vancann...@wisa.be said:
>
> You must remove the quotes around 'outputfile.org':
>
>
> Status:=ExecuteProcess('/path/to/oggenc',['-Q','--output=outputfile.org','tempfile.wav']);
While better, this is afaik not required per se, the executing binary can
strip th
brian wrote:
At least IMHO, having to quote the entire parameter string, not just the
value, is anything but "common whitespace and quote rules".
I am pretty sure that I have had to deal with this in the past on unix,
writing shell or Perl scripts i.e. not in the context of FPC. It might,
in
On 09/09/2011 04:02 AM, Felipe Monteiro de Carvalho wrote:
The quotes are bash commands, they are not part of command line. I
wrote on this topic not long ago, but for TProcess:
http://wiki.lazarus.freepascal.org/Executing_External_Programs#Parameters_which_contain_spaces_.28Replacing_Shell_Quot
In our previous episode, Anton Shepelev said:
>TProcess:
>If the command to be executed or any of the
>arguments contains whitespace (space, tab
>character, linefeed character) it should be
>enclosed in single or double quotes.
It should now be possible
Andrew Haines:
> I suspect that the oggenc command is failing
> because TProcess behind the scenes is splitting
> --output="outputfile.ogg" into two params.
Yes, indeed. It is also mentioned on the WIKI:
http://wiki.freepascal.org/Executing_External_Programs
(see section
"Para
The quotes are bash commands, they are not part of command line. I
wrote on this topic not long ago, but for TProcess:
http://wiki.lazarus.freepascal.org/Executing_External_Programs#Parameters_which_contain_spaces_.28Replacing_Shell_Quotes.29
--
Felipe Monteiro de Carvalho
__
On Fri, 9 Sep 2011, Marco van de Voort wrote:
In our previous episode, brian said:
write a batch file for the actual conversions.
What are the commands?
mpg321 -q -w "tempfile.wav" "inputfile.mp3"
oggenc -Q --output="outputfile.ogg" "tempfile.wav"
between the ExecuteProcess and fpSystem c
In our previous episode, brian said:
> write a batch file for the actual conversions.
>
>
> What are the commands?
>
> mpg321 -q -w "tempfile.wav" "inputfile.mp3"
>
> oggenc -Q --output="outputfile.ogg" "tempfile.wav"
> between the ExecuteProcess and fpSystem calls, I just commented out
> the
16 matches
Mail list logo
