libconf-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libconf-dev] Re: shell template and whitespace around the =


From: dams
Subject: Re: [Libconf-dev] Re: shell template and whitespace around the =
Date: Sun, 15 Jun 2003 02:18:41 +0200
User-agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux)

"Brian J. Murrell" <address@hidden> said:

> On Sat, 2003-06-14 at 11:42, address@hidden wrote:
>> that's right! I'll look at it and try to build a generic keyvalue template. 
>> If
>> you need help to build the postfix template, just ask :)
>
> Got the keyvalue template and have built (er, I mean ripped off -- from
> Shell) a KeyValue Glueconf class.  I am able to parse the Postfix
> main.cf file with it but for one thing.
>
> It seems, in the Postfix main.cf file anyway, that keys and values are
> allowed to be separated by newlines/^tabs as in:
>
> debugger_command =
>        PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
>        xxgdb $daemon_directory/$process_name $process_id & sleep 5

hey! I'm glad you saw that, I was working on it :)

I have commited a postfix libconf template, and a test suite. The postfix
template handles the multiline. I have added 2 special variables into
Libconf.pm to make it easier, $switch_to_next_atom and $switch_to_prev_atom.

Their use is easier than deal with $keep_atom.

>
> (note that the last 2 of the three lines is tab prefixed).
>

I have asked a friend of mine about it, it seems that any \s character (space,
tab...) at the very beginning of the line means that it's the same atom.


-- 
dams




reply via email to

[Prev in Thread] Current Thread [Next in Thread]