Re: parser problem

[martin f krafft <madduck@madduck.net>]

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

also sprach martin f krafft <madduck@madduck.net> [2004.12.21.1517 +0100]:
> chmod'd to 660. Seems like the newline causes udev to ignore the
> previous match specification.

So noticing the recent announcement where multiline is a feature
request, I tried to figure out why I thought that it can be
multiline in the first place. My first guess was because of the
commas, which seem to be syntactic sugar without a real purpose.

My second guess comes from Lindsay saying:

  "I see no problem with having owner, group and mode spec"d in udev
  rules files. Certainly this furthers the the purpose of
  centralization. The syntax of the file is reasonably forgiving,
  and anyone wanting a greater degree of order could format it to
  personal taste so as to make it more readable."

More readable to me is <80 columns.

Oh well, apparently we now have to define permissions policy in
column 190. Yeah udev!

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
spamtraps: madduck.bogus@madduck.net
 
"never speak disrespectfully of society.
 only people who can't get into it do that."
                                                        -- oscar wilde

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]