>>>>> "RBAK" == Roger B A Klorese <rogerk@QueerNet.ORG> writes:
RBAK> The problem is that, for many of us, there are printed or on-line
RBAK> subscription instructions (that are semi-followed) in dozens of
RBAK> places, and we pay the price for it every day.
I have that problem too, and had managed to forget about it.
So it comes down to making a list of boneheaded things that users do when
communicating with the server and seeing if each can be remedied without
collateral damage.
-----
<< command args >>
seems easy (s/^<<\s*(.*)\s*>>$/$1/) but:
1) How does this possibly interfere with <<< TAG?
2) Does this ever appear as a legitimate quote? I.e. might the user _not_
want this to execute because they're quoting the server?
3) Is it really ever on one line? What happens to:
<< command args
>>
or
<<
command >>
?
Let's not think about
<< command
args >>
----
> command args
s/^>\s*//;
1) Does anyone (besides owners quoting a configshow) ever actually do this
and expect the command to execute?
2) How would this impact the ignoring of quoted token messages while
looking for a trailing "accept"? (We always include the "accept" in
quotes, so technically it should never appear bare in the message unless
the user typed it.
3) Wouldn't this just cause more harm than good? The quoting protects us
from ever seeing a spurious command in a big quoted reply sent to
Majordomo.
----
While we're at it:
subscribe listname-digest
We _must_ handle this.
if valid_list($list) then handle as normal.
if ($list =~ /(.*)-digest/ && valid_list($list)) then {$mode .= '-digest'};
----
echo | mail listname-digest-subscribe
echo | mail listname-subscribe-digest
These seem to be reasonable guesses for someone to make. Perhaps an
additional setting for the 'aliases' variable?
----
I'm sure there are many others, but most of the ones I see come from the
bogus Mj1 help files:
subscribe list [<me@my.host>]
Aargh!
- J<
Follow-Ups:
References:
|
|
