Ken Hornstein <[EMAIL PROTECTED]> writes:
> >> I've included a MIME pointer to the patch below. Comments welcome.
> >> Doug has fixed my subscription to the list, so you can feel free to
> >> reply to the list with comments.
> >
> >What was wrong, out of curiosity?
>
> Let's see ....
>
> Well, I didn't realize that whatnow parsed switches for send, so
> I had to add -sasl, -saslmech, and -user to whatnow. I didn't
> notice this for a while because I use exmh most of the time, which
> just calls send directly. Also, I forgot to initialize pass to NULL
> before calling ruserpass() in the POP and SMTP code (which worked
> on some architectures, but failed on others).
Actually I meant what was wrong with your subscription to the list (in case
it comes up again).
> >> (BTW, who do I talk to if I want to get this into the distribution?)
> >
> >Well, we don't really have a single "fearless leader", so it's basically
> >whichever of the folks with write access (Dan Winship, Doug Morris, Ruud de
> >Rooij, Shantonu Sen, and I) takes the initiative to stick it in. If no one
> >does, you can pester us on the list.
> >
> >And like I said before, you could certainly ask Doug for your own
> >write-access.
>
> I might do that. I am still mulling about some minor UI issues (if you
> add -sasl on the command line, but it's not supported, what should
> happen?)
As I recall, most or all of the command-line options that are enabled at
configure/compile-time time right now just act as if they don't exist if you
don't enable them. Even the man pages are sed'ed to remove any reference to
the non-supported options.
There's some merit to that approach, but I'd prefer putting the stuff in the
man page and just including a note that an option isn't supported unless nmh
was compiled with support for it. I'd also put the option in the command's
--help output unconditionally, and have the option print out a message that
nmh wasn't compiled with support for it if that's the case.
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
[EMAIL PROTECTED] | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
