Re: "Too long" error due to command line

On 30 Dec, Nicholas Clark <[email protected]> wrote:

> Moving/symlinking either/both the perl script or the perl binary nearer to
> $ will work around the problem for a bit by making the paths shorter.

I defined a *$Path variable, and used a pseudo-filing system.
But the problem with this is that I can no longer drag'n-drop
the filename to the taskwindow, otherwise the full pathname
would be written.

> I believe that RISC OS 4 raises the OSCLI limit from 255 to 1023 characters.

This is still ridiculous...

> If you're not calling your perl script from an obey file you might be best
> to investigate the DDEUtils module and the extended command line that it
> provides. perl (courtesy of UnixLib) will automatically read these, so all
> you'd need to do is make the calling program set an extended command line.

There was no calling program. I typed the command from a taskwindow.
But can LineEditor use this extended command line?

-- 
Vincent Lefèvre <[email protected]> - PhD student in Computer Science
Web: <http://www.vinc17.org/> or <http://www.ens-lyon.fr/~vlefevre/> - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International
des Jeux Mathématiques et Logiques, TETRHEX, etc.