>>>>> "WRD" == "William R Dickson <-- System Administration" <firstname.lastname@example.org>> writes:
WRD> Okay, here's the latest version; comments welcome (and desired). Some
WRD> stuff still needs to be covered:
WRD> - It would be helpful if I had an understanding of regular expressions
WRD> so I could stick some into examples. Can anybody point me at a
There's the mini-tutorial in the list-owner-info document that comes with
WRD> - In the 'aux.....' commands, what is the function of the
WRD> "allmatching" option?
I don't think it applies to the aux* functions, just ones that remove users
from lists (i.e. auxunsubscribe and unsubscribe). It's intended use is
alongside regexp matches. Normal behavior removes only the first matching
entry; with allmatching, it removes every matching entry. Think:
approve blah unsubscribe-regexp-allmatching .*\@aol\.com
Contrast that with Majordomo1, which if it finds more than one matching
entry (even though it doesn't do any regexp stuff, this can still happen if
it screws up or you manipulate the file by hand) will just bomb without
WRD> - Where is the EDITOR environment variable set?
It's an environment variable; you set it in your shell. EDITOR is the
normal way in Unix to choose a default editor for all programs that need
WRD> Would there be any use for an HTML version of the files? Perhaps the
WRD> installer could stick 'em into a user-defined directory?
Not right now, but I would consider making POD versions and using
pod2(text|html) to convert them to text or HTML on the fly (or during the
installation). But lets stick to text for now. Check the perlpod manpage
for more info on POD.
A bit of this has changed (especially surrounding the addr_xforms stuff,
since it is now not per-list) but I'm going to wait until things settle
down a bit before going back to the docs.