Ken Hornstein k...@pobox.com writes:
- Jerry Peek, this is for you, assuming you're still around. The
MH/nmh book is a great resource, but it hasn't been updated in a
while. Would you be interested in updating some stuff for some of the
newer nmh features? I'm thinking specifically of the
Ken == Ken Hornstein k...@pobox.com writes:
Ken - I think we have enough new stuff that a new release based on
Ken the tip of master is worthwhile. Let's call it 1.5, since it
Ken doesn't feel fresh enough to me to make it a 2.0. I'd rather
Ken invest my energy in doing that
On 2012-02-03, at 9:42 AM, Ken Hornstein wrote:
I propose we have
a new .mh_profile entry that is used as the default From: when one
isn't supplied in a draft. Objections?
I would rather we use the existing components framework to do this. Growing a
new option is just bloat, IMO. Thus my
On 2/3/2012 6:49 PM, Lyndon Nerenberg wrote:
On 2012-02-03, at 9:42 AM, Ken Hornstein wrote:
I propose we have
a new .mh_profile entry that is used as the default From: when one
isn't supplied in a draft. Objections?
I would rather we use the existing components framework to do this.
I propose we have a new .mh_profile entry that is used as the default
From: when one isn't supplied in a draft. Objections?
I would rather we use the existing components framework to do this.
Growing a new option is just bloat, IMO. Thus my comments a few weeks
back about having the installer
i think that we should not emit a From: without an @FQDN, or fail to
emit a From:. if the components file did not give us a From: then we
should autogenerate From: `whoami`@`hostname` and let the gods sort it
out.
So that's what we _used_ to do. I kinda punted on that a bit. Turns out
that
On 2012-02-03, at 10:59 AM, Ken Hornstein wrote:
I thought about this ... but that would mean we ditch the installed
system components files completely, and it's not clear what we do
for existing users.
I would use the system-side components as the template to populate the user's
components
I was under the vague impression that ORA gave Jerry back the book and
Indeed, its now GPL: http://rand-mh.sourceforge.net/book/
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
On 2012-02-03, at 10:59 AM, Ken Hornstein wrote:
I thought about this ... but that would mean we ditch the installed
system components files completely, and it's not clear what we do for
existing users.
I would use the system-side components as the template to populate
the user's components
On 2/3/2012 7:19 PM, Ken Hornstein wrote:
Now that I've thought about it some more and used the current code,
I think the precedence should be (in order of higher precedence to
lower precedence):
1) From: line in draft
2) Setting in .mh_profile
3) `whoami`@`hostname`
The alternative was
Alright let me see if I've captured the consensus:
- Make the default email address be (in decreasing precedence order)
- A knob in .mh_profile (Local-Mailbox ?)
- `whoami`@mts.localname
- `whoami`@`hostname`
- All drafts get run through mh-format
- All default component files now
- If there is a draft without a From that is fed to post, it will error
erp? What sort from From is it going to require?
I currently use
From: me
And it DWIM, while giving me the ability to quickly change it in a draft
to another of my identities
- If there is a draft without a From that is fed to post, it will error
erp? What sort from From is it going to require? I currently use
From: me
No requirements other than it exists and is parsable by nmh (any
From: line that exists today has to be parsable by nmh). If you
just have that,
On Fri, Feb 3, 2012 at 9:42 AM, Ken Hornstein k...@pobox.com wrote:
realized that we should deal better with this. I propose we have
a new .mh_profile entry that is used as the default From: when one
isn't supplied in a draft. Objections?
Isn't that what the (now poorly named) Signature
Isn't that what the (now poorly named) Signature mh_profile entry
does? I used to use it for this purpose, anyway.
All that Signature does is serve as a replacement for the GCOS field
from /etc/passwd. mh-profile(5) specifically says to not put an address
in there. So we need something else.
15 matches
Mail list logo
