comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: Length of command line input
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: Length of command line input [message #49551 is a reply to message #49548] Thu, 03 August 2006 10:51 Go to previous messageGo to previous message
larkn10 is currently offline  larkn10
Messages: 10
Registered: July 2006
Junior Member
TimLS wrote:
> I couldn't find the answer to this in the online documentation but
> perhaps someone has seen this before, or can suggest a good work
> around.
>
> I have a procedure which takes lots and lots of keywords, many of which
> are really long filenames, e.g.
> test_program,input1='really_long_filename1',input2='really_l ong_filename2',....
>
> Eventually IDLDE running under linux decides that it has had enough and
> essentially only accepts the first 500 characters (approximately) that
> have been typed into the command line. (Trying to run it as a batch
> file has the same effect).
>
> Is there a limit on the length of the command line, and is it possible
> to extend it anyhow?
>
> Thanks, Tim

I think there is a limit to the length of the command line (I thought
256 characters
but I could be wrong.)

To solve your problem, how about

f1 = 'really_long_filename1'
f2 = 'really_long_filename2'
f3 = 'really_long_filename3'
etc.

test_program,input1=f1,input2=f2,....

-Larry
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: tile of IDLgrAxis
Next Topic: Interpolation question

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Oct 11 09:03:36 PDT 2025

Total time taken to generate the page: 0.47999 seconds