Long-style-option support in ezmlm-make

Tullio Andreatta ML <[email protected]>
Newsgroups gmane.mail.ezmlm
Organization Wave Technologies S.r.l.
Message-ID <[email protected]>
Christian Lerrahn:
>> is there a reason why the -T switch of ezmlm-reject cannot be set
>> through ezmlm-make?

Bruce Guenter:
> Most likely just because nobody thought it was terribly important, and
> ezmlm-make ran out of flag letters (All of a-y are currently used).  I
> am working to help reduce this issue.

I wrote a patch to support --long-style-options in ezmlm-make.
I used this patch to implements some local ezmlmrc tricks.

With this patch:

- you can define --long-style aliases at compile time for one-letter
   combinations (examples: "--moderate-others" for '-mu' or
   "--archive-access=subscribers" for '-ag' or "--no-archive" for '-A');
   (see make_lopt.h)

- 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#>'
   ...); and you can use either '^{option}' and '{no-option}' syntax;

- you can use OR operand (example:
   ...
   </#uy|muY/>
   |<#B#>/ezmlm-clean -R '<#D#>' || exit 0
   ...);
- you can use long option value (example: using
   ezmlm-make ... --prefix=custom-prefix ...
   ...
   </prefix#fE^{prefix}/>
   [<#L#>]
   </#E{prefix}/>
   [<#$#>]
   ... writes "custom-prefix" in LISTDIR/prefix).

This patch is backward compatible -> no modification are needed in
current ezmlmrc.
This patch has not been extensively tested (usually I run
ezmlm-make once, and I never edited options in production
lists - only during tests).



-- 
Tullio Andreatta

Disclaimer: "Please treat this email message in a reasonable way, or we
     might get angry" ( http://www.goldmark.org/jeff/stupid-disclaimers )
ezmlm-idx-5.1.0-make-longoptions.gz (application/x-gzip-compressed, 3.5 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.