Re: Long-style-option support in ezmlm-make
Bruce Guenter <[email protected]>
| Newsgroups | gmane.mail.ezmlm |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Oct 23, 2006 at 04:21:24PM +0200, Tullio Andreatta ML wrote:
> I wrote a patch to support --long-style-options in ezmlm-make.
Interesting.
> - you can use long-style options in ezmlmrc (example:
> ...
> </editor#^0{allow-bcc}/>
> |<#B#>/ezmlm-reject -T '<#D#>'
> </editor#^0^{allow-bcc}/>
> |<#B#>/ezmlm-reject '<#D#>'
This is reasonably good syntax, and retains backwards compatibility. I
had started using a different syntax, but it would break existing lists,
which is obviously bad.
> ...); and you can use either '^{option}' and '{no-option}' syntax;
I don't think adding the {no-*} syntax has much value except to cause
confusion.
> - you can use OR operand (example:
> ...
> </#uy|muY/>
> |<#B#>/ezmlm-clean -R '<#D#>' || exit 0
> ...);
Interesting, but not terribly useful.
> - you can use long option value (example: using
> ezmlm-make ... --prefix=custom-prefix ...
> ...
> </prefix#fE^{prefix}/>
> [<#L#>]
> </#E{prefix}/>
Shouldn't this be:
</#fE{prefix}/>
?
> [<#$#>]
> ... writes "custom-prefix" in LISTDIR/prefix).
What is <#$#> here?
> This patch has not been extensively tested (usually I run
> ezmlm-make once, and I never edited options in production
> lists - only during tests).
From what I can see, the extended flags don't (and can't) get saved for
future runs (except for those that correspond to existing flags).
This mechanism will not be added to ezmlm-idx as-is. I am actually
trying to move *away* from the use of complex ezmlm-make invocations
(and consequently the use of ezmlmrc files) to configure mailing lists.
Instead, I will be placing configuration options into individual files
in the list directory (much the same as "archived" and "moderated" etc)
that can be created and removed with ease.
As a first step, the next version of ezmlm-idx will attempt to move all
command-line options out of the command files (ie "editor" etc). I've
already handled the most obvious ones in the same way that the
DIR/confirmpost file works with ezmlm-store -y/-Y: If the command line
option is given, it forces the option off or on. Otherwise, the program
looks for the file. This will allow for backwards compatibility with
existing lists (that use the command line options).
It will still, however, be necessary to run ezmlm-make -+ when editing a
list to set the contents of DIR/flags and the program lists in the
command files, but that too will disappear in future versions.
--
Bruce Guenter <[email protected]> http://untroubled.org/
OpenPGP key: 699980E8 / D0B7 C8DD 365D A395 29DA 2E2A E96F B2DC 6999 80E8
I do custom software development. Email me for details.
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFW+LA6W+y3GmZgOgRAj/tAKCj6zr84/lxFz+IxSFIcQt0UR7QjACdGch1 wbbvJTA8TgPztNvqY9foTuk= =zoS5 -----END PGP SIGNATURE-----