1) command line (-locale)
2) mh-command-specific profile entry (.mh-profile)
3) environment ($NMH_LANG)
4) profile default override (.mh-profile)
5) OS environment default (locale())
It's arguable about the ordering of (2) and (3). But if I really needed
this level of control in real life, I can't see how I would have both in
play.
OK. I'm not going to add a -locale switch, that seems to me to move this
too close to nmh. I like the locale profile component. Let me ask those
who might use it: do you also want the NMH_LANG environment variable? I'd
rather not add a feature that won't be used.
If we drop (1), then (3) is the only alternative, so I would say drop (1), and
reverse (2) and (3).
The overhead of $NMH_LANG isn't even measurable, and the code path is trivial.
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers