[coLinux-devel] Re: TO-DOs for Release

[Jani T. <re...@lu...>]

Dan Aloni kirjoitti:
> On Mon, Dec 06, 2004 at 09:38:29AM +0100, Leeuw van der, Tim wrote:
> 
>>I would seriously re-consider that idea to drop config-files. On windows, you cannot pass command-line arguments longer than 4000 characters. And I've ran into that limit with other software.
>>If you build up an extensive config for coLinux, I'm very sure that ppl will run into that limit with coLinux too.
> 
> 
> This problem is also being dealt with in other command line programs, using 
> the '@' method. For example:
> 
>     program param1 param2 @params.txt
> 
> The program takes the rest of the its arguments from 'params.txt'. You can regard
>  
> coLinux currently doesn't support this argument passing method, but it will in 
> one of the next revisions.
>  
> 
>>Also, I've found it to be very, very, very unmanageable, to start programs with very long command lines. If only because your average editor doesn't always handle things the right way and often breaks lines in the wrong place -- or because your preference is not to show lines with linewrap by default.
>>
>>For me, config-files make things much more accesible, manageable. And they can more easily be taken from one platform to the next. 
> 
> 
> You can regard 'params.txt' as a manageable multi-line configuration file,
> with the ability to temporarily override settings from the command line.

I rather would do it vice-versa: commandline param overrides one in 
configuration. That way you could keep generic settings (that could be 
managed with fancy GUI if needed) and then variable parameters could be 
entered to commandline.

But this as a solution this is far most better. It's just matter of 
taste whichway around it handles priorities: paramfile or commandline param?

-- 

Jani Tiainen