On Monday 14 May 2007 21:35:04 Eric S. Raymond wrote:
> > If it is really a problem we should probably use some more conventional
> > filenames like _main.cfg instead of %main.cfg for example.
>
> Alas, it appears the ls(1) sort algorithm ignores all leading
> non-alphanumerics.
It depends on your
John McNabb <[EMAIL PROTECTED]>:
> Why not just have a single file name, main.cfg, and if it exists only
> process it automagically? Internally the main.cfg could define any
> order that is needed. Do we really need to have some sort of
> automatic ordering of a whole bunch of files?
%final.cfg
Why not just have a single file name, main.cfg, and if it exists only
process it automagically? Internally the main.cfg could define any
order that is needed. Do we really need to have some sort of
automatic ordering of a whole bunch of files? I suspect that there is
some IRC conversation that t
[EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> I've done a quick test at work under Windows XP, i could create a %main.cfg
> file.
The next step should a fix for the get_files_in_dir() to make it detect
and handle %main.cfg as Unix does.
> If it is really a problem we should probably use some more con
On Mon, May 14, 2007 at 12:18:16PM -0400, Eric S. Raymond wrote:
> I have written and tested Unix support in the WML preprocessor for two
> extensions:
>
> %final.cfg: if a directory named 'dir' contains a %final.cfg, then
> when processing the files in dir is invoked by the
>
I have written and tested Unix support in the WML preprocessor for two
extensions:
%final.cfg: if a directory named 'dir' contains a %final.cfg, then
when processing the files in dir is invoked by the
construct {dir}, %final.cfg will be processed last.