Tom Browder:
> On Tue, Mar 22, 2016 at 11:56 AM, Wietse Venema <wie...@porcupine.org> wrote:
> > Tom Browder:
> >> I would love to be able to use comments on the same line as conf and map
> >> file entries. That has probably been requested before, but is it a
> >> definite WILL NOT?
> >
> > Definitely. That would require some kind of quoting mechanism to
> > indicate which "#" are part of the data which "#" are not, and that
> > quoting mechanism would break compatibility with existing configurations.
>
> Okay, after reviewing the wide latitude for e-mail addresses I understand.
>
> But, couldn't there be a user option to build Postfix to allow such
> (or maybe define some special comment character or characters such as
> the common '//' or '--')? It shouldn't change the default behavior
> and wouldn't disturb other installations.
In practice, the only comment character that makes sense in as
Postfix file is the "#"; anything else will just confuse the hell
out of people. So there would need to be a way to turn on/off
trailing comments for an individual file. That would require some
kind of modeline support (a line with special sequences that change
how the file will be processed).
/etc/postfix/main.cf:
# This modeline is needed otherwise trailing comments won't work
# in main.cf (chicken and egg problem).
# postfix: trailing_comments=yes
trailing_comments = yes # Global default
/some/other/file:
# This file contains # in the data.
# Override the "trailing_comments = yes" setting in main.cf.
# postfix: trailing_comments=no
stuff that contains a # character
Is this really easier to use? That is not obvious to me.
Modeline support will break compatibility with every existing
configuration that has lines starting with "# postfix:".
Making "trailing_comments = yes" the built-in default will break
compatibility with every existing configuration that has # in the
data.
Wietse
