Re: byte-compile-nogroup-warn effectively disabled

[Stefan Monnier]

>     Sorry, I haven't followed this. But IIUYC, I think it would be
>     a mistake to automatically assign an option or face the group that
>     was last specified before it in the same file.

>     What for? What is gained? Sounds like an invitation for user
>     errors that won't necessarily be noticed right away. It might not
>     be an important error to assign the wrong group, but why encourage
>     that possibility?

> That is what I feel, too.  Omitting the :group is no big savings in
> effort; writing it gives you a chance to think about it.

I know.  And we've already reached the conclusion that we have to agree
to disagree on this one.


        Stefan