[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] It's mh_profile(5) and mts.conf(5).

From: valdis . kletnieks
Subject: Re: [Nmh-workers] It's mh_profile(5) and mts.conf(5).
Date: Sun, 28 May 2017 16:54:23 -0400

On Sun, 28 May 2017 11:36:28 +0100, Ralph Corderoy said:

> The files they document are $HOME/.mh_profile and /etc/nmh/mts.conf.  I
> don't think mh-profile(5) and mh-tailor(5) should exist or be referred
> to;  it's just confusion and clutter.

Keep mh-profile.  It's useful to have all (or almost so) things possible in
a config file documented in one place. Also, where exactly are you planning to
exile all the "standard profile entries" to?  And the Description section
that documents the way to continue lines, and the status of blank lines, etc?
Also, since there are a lot of "applies to most but not all" entries, like:

      locale: locale
            Set  the  locale for all nmh programs except post, install-mh, and
            slocal.  See the LC_ALL,  LC_CTYPE,  and  LANG  variables  in  the

there needs to be a place where the exceptions are documented.

While reading the manpage, I noticed this:

       Local-Mailbox: Your Username <address@hidden>
            Tells the various MH tools what your local mailbox  is.   If  set,
            will be used by the default component files by tools like comp and
            repl to construct your default ?From? header.  The text used  here
            will  be copied exactly to your From: header, so it should already
            be RFC 822 compliant.  If this is set, the Signature profile entry
            is  NOT used, so it should include a signature as well.  (profile,
            default: address@hidden)

Wait, what?  Setting Local-Mailbox: disables Signature: ??!?

On further reading, finding the Signature: entry, we discover that they
don't mean 'signature' in the sense that exmh and most other MUAs use it, for
a file to be auto-appended to the message like a .sig file.  They mean the
friendly-name field in the From: line.

And *that*, my friends, is why you want to have all of the stuff in one
place, so you can easily cross-reference and figure the semantics out.

(Though this *still* leaves the question of whether the Signature: block
needs proper quoting if it contains non-ascii or rfc-problematic punctuation....

Attachment: pgp5PfZ0Iui09.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]