Re: [commons-exec] API discussion: Quoting of arguments: why is it enabled by default?

Hi, thanks for your answer. However, I'm not sure I understand the exact intent of the quoting. what problem is it supposed to solve ? sami Quoting Siegfried Goeschl : > Hi Sami, > > looking though the SVN history > > +) quoting of the arguments was always turned on > +) I added the flag were

Re: [commons-exec] API discussion: Quoting of arguments: why is it enabled by default?

Basically, my use case is to execute (on linux) : ffmpeg -i /tmp/myfile and in case of a space ffmpeg -i "/tmp/my file with spaces" Let's say I called ffmpeg using Runtime.exec, the command array I would pass would be : {"ffmpeg", "-i", "/tmp/my file with spaces"} now, using commons exec, I

[commons-exec] API discussion: Quoting of arguments: why is it enabled by default?

I did not notice all commons-* were using the same mailing-list, so here is the correct subject along with the original message Sorry for the inconvenience, sami - Forwarded message from Ralph Goers - Date: Mon, 16 Feb 2009 18:22:20 -0800 From: Ralph Goers Reply-To: Commons Deve

API discussion: Quoting of arguments: why is it enabled by default?

Hi, I am wondering why the quoting of arguments (if they contain spaces) is enabled by default. This is certainly not the behaviour I was expecting while using the API, as passing a filename as an argument will just fail if it is surrounded with quotes. regards, sami dalouche --