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 #49548 is a reply to message #49546] Thu, 03 August 2006 12:13 Go to previous messageGo to previous message
JD Smith is currently offline  JD Smith
Messages: 850
Registered: December 1999
Senior Member
On Thu, 03 Aug 2006 10:00:04 -0700, 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?

Yes, there is a limit, and I believe it's 512 characters, depending on
device. You can turn off IDL command line editing with !EDIT_INPUT=0,
which should make the limit "infinite", but this also disables command
line "background" processing of widget events. You can always compile it
to a main level routine as well.

JD
[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 13:37:55 PDT 2025

Total time taken to generate the page: 0.00911 seconds