Ken Hornstein writes:
It is possible to keep almost unchanged state with addition of
one more clause to mhbuild like pair #off #on which marks the
region where ^# is not interpreted as directive.
But to me it seems dumb that # characters can't be in the
beginning of a line, and having
Suppose, you use automimeproc: 1 and you want to include (as a
part of the message) some lines from program source, shell script
or whatever.
[...]
I understood what you meant fine; I just think you misunderstand
me. My basic proposal is:
- Make automimeproc: 1 be turned on always
- Make it so
aleksander wrote:
Ken Hornstein writes:
It is possible to keep almost unchanged state with addition of
one more clause to mhbuild like pair #off #on which marks the
region where ^# is not interpreted as directive.
But to me it seems dumb that # characters can't be in the
ken wrote:
to answer ken's question: i use automimeproc for the directives, and
am willing to reformat mail slightly to move leading '#' characters when
i get errors[1][2]. and i prefer not to have to type mime at the
whatnow prompt, because i'm sure it would result in my recipients
I've been thinking a bit of this and I can see (as a user not
programmer) a couple of possibilities.
It is possible to keep almost unchanged state with addition of
one more clause to mhbuild like pair #off #on which marks the
region where ^# is not interpreted as directive.
Yeah, to me that's
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
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
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 message.
