Raul Miller <email@example.com> writes:
> But you can do a lot with a decent parser.
But what do you do about config files that are just perl, or python,
or elisp? There's no way you can write a parser that can predict what
the code in the file will do in the general case, and we can't really
mandate what upstream developers do just to accomodate our choice of
Also, does linuxconf handle nested syntaxes like lisp or html, or just
Using a tagged template scheme like Craig proposed wouldn't completely
solve the problem either, but it might make it a lot more
straightforward to handle most of the cases.
Rob Browning <firstname.lastname@example.org>
PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org