In the .mh_profile some entries specifies programs like:
Editor: vim-mail
moreproc: less
postproc: /usr/lib/mh/post
Some of those programs require options or parameters but
apparently this is not accepted.
I need moreproc to be "less -force" but show (nmh-1.3) refuses
this.
Workaround is to ma
My wife pointed out to me today that for the past seven years (!) since
the Linux distribution we use switched to UTF-8, when she sends messages
containing non-ASCII characters they show up as gibberish for many of
the recipients---but not for me. I'm also using a UTF-8 locale, which
explains why I
Hi Joel,
> Is there a solution to this with nmh 1.4 or 1.5?
I've changed my mail/components, etc., to have these three MIME headers
in and then I create a UTF-8 file in vim. I need to delete them if I'm
going to `mime' at the whatnow(1) prompt, e.g. for attaching a file,
because it quite rightly
Joel Uckelman writes:
> My wife pointed out to me today that for the past seven years (!) since
> the Linux distribution we use switched to UTF-8, when she sends messages
> containing non-ASCII characters [..] and that nmh is
> producing messages which lack any headers indicating that the contents
Hi max,
> Why not set in .mh_profile
> automimeproc: 1
I like to look over the mime'd draft before sending to check I got the
directives right.
Cheers, Ralph.
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinf
Ralph Corderoy writes:
> Hi max,
>
> > Why not set in .mh_profile
> > automimeproc: 1
>
> I like to look over the mime'd draft before sending to check I got the
> directives right.
Well, it seems that both approaches can coexists if buildmimeproc
would do nothing in case of already MIMEfied mes
>Well, it seems that both approaches can coexists if buildmimeproc
>would do nothing in case of already MIMEfied message. Instead of
>error reporting.
There is one caution here ... if you have a line that begins with a "#"
that is NOT an mhbuild directive then you'll get an error. That's fine for
Hi!
At the time of the 1.4 release I mentioned, that Nick Rusnov (CCed) is
still the debian maintainer of nmh. While he is indeed listed there as
of today[1], he obviously didn't find the time to update the debian
package.
1: http://packages.qa.debian.org/nmh
As debian is going to freeze quite s
On Tue, 29 May 2012 01:37:44 +0200, Harald Geyer writes:
>Is there any DD on this list, who could sponsor an upload of 1.4 or 1.5RCx?
here. i'm the DD maintaining exmh, so nmh is close to the heart
and i'd be happy to maintain it.
i'll check with nick if he's ok with co-maintaining.
regards
az
>I need moreproc to be "less -force" but show (nmh-1.3) refuses
>this.
Yeah, I guess what happens there is mhl (or whatever) is trying to
exec("less -force"). Which as you've noted doesn't work.
Other people have complained about this as well. But in this case you
could just set the environment
>>Is there any DD on this list, who could sponsor an upload of 1.4 or 1.5RCx?
>
>here. i'm the DD maintaining exmh, so nmh is close to the heart
>and i'd be happy to maintain it.
So I haven't really been itching to get 1.5 out the door for various
reasons ... but if releasing it sooner rather than
>Sure, it COULD do that. Sounds like you're volunteering to write
>the code; great! :-)
I hack perl, not C. I did quickly grep the perl code base for it though,
but being on a tablet at the moment could not dive too deeply.
nmh is non-GNU, but perl is dual-licensed under the Artistic License.
>kn
>>Sure, it COULD do that. Sounds like you're volunteering to write
>>the code; great! :-)
>I hack perl, not C. I did quickly grep the perl code base for it though,
>but being on a tablet at the moment could not dive too deeply.
>nmh is non-GNU, but perl is dual-licensed under the Artistic License.
Could nmh not do with such parameters what perl does for
system()/exec(), auto-splitting the string? In the off
chance that someone's installed binaries in a path with
a space they can escape the space, same as they would in
a shell...
___
Nmh-workers ma
>Could nmh not do with such parameters what perl does for
>system()/exec(), auto-splitting the string? In the off
>chance that someone's installed binaries in a path with
>a space they can escape the space, same as they would in
>a shell...
Sure, it COULD do that. Sounds like you're volunteering
15 matches
Mail list logo
