[Bioperl-l] CommandExts and arrays

[Ben Bimber]

as long as the limitation is known, i dont see it as a big problem.



On Mon, May 24, 2010 at 2:38 PM, Dan Kortschak
<dan.kortschak at adelaide.edu.au> wrote:
> Hi Dave,
>
> You are right, spaces are not allowed - they are actively stripped from
> filenames (the other option would be to escape or otherwise quote them -
> the is certainly doable, is there enough of a call to do this?).
>
> You can use last_execution() to see what was attempted to be run, this
> should show the filenames (and everything else) that were used in the
> IPC call.
>
> cheers
> Dan
>
> On Mon, 2010-05-24 at 12:00 -0400, Dave Messina wrote:
>> Message: 2
>> Date: Mon, 24 May 2010 15:00:56 +0200
>> From: Dave Messina <David.Messina at sbc.su.se>
>> Subject: Re: [Bioperl-l] CommandExts and arrays
>> To: Ben Bimber <bbimber at gmail.com>
>> Message-ID: <CB6127B6-FFAC-4DDA-B6DE-88A8C087855B at sbc.su.se>
>> Content-Type: text/plain; charset=windows-1252
>>
>> > ok, i put in that bug.
>>
>> Thanks.
>>
>>
>> > why exactly does having the asterisk indicate
>> > this is a bug?  i thought the asterisk indicated that multiple
>> values
>> > were allowed for that argument?
>>
>> Ah okay, my ignorance of this module is showing. :)
>>
>>
>> > on a related note, are we supposed to be able to pass file names
>> that
>> > have spaces to command exts?  on the few cases where this came up, i
>> > have never seemed to get this to work right, so i just got rid of
>> the
>> > spaces.
>>
>> Sorry, I don't know.
>>
>>
>> Paging Mark Jensen ? have you got a moment to look into this?
>>
>>
>> Dave
>
>