Re: [Nmh-workers] Maybe time for a new release?

Conrad wrote: > Yes, seems so; I guess I'd just like a "best practice" section in the > mhfixmsg man page which shows (for example) a recommended command line > invocation (more-or-less covered a few emails back) and a procmail recipe. There's been a procmail recipe in the man page since March

Re: [Nmh-workers] Maybe time for a new release?

Jerrad wrote: > I use slocal with rcvstore and at various times either MIME-hooks or the > following .mh_profile entries > > add-hook: /usr/local/bin/mhfixmsg > mhfixmsg: -decodetext 8bit -reformat -replacetextplain Note that -decodetext 8bit and -reformat are defaults, so they're not

Re: [Nmh-workers] Maybe time for a new release?

Norm wrote: > The bulk of the non-spam mail I receive still has a utf-8 or a quotedPrintabl > e part. I would like to apply UNIX text processing tools (grep, wc, sort, > uniq, perl, etc) to these messages. It would be nice if the next release made > that reasonably easily possible. That's the

Re: [Nmh-workers] Maybe time for a new release?

Ralph Corderoy writes: >Hi Ken, > >> Norm wrote: >> > The bulk of the non-spam mail I receive still has a utf-8 or a >> > quotedPrintable part. I would like to apply UNIX text processing >> > tools (grep, wc, sort, uniq, perl, etc) to these messages. >> >> I ... think the

Re: [Nmh-workers] Maybe time for a new release?

>In principle I'd *like* to run mhfixmsg on email as it's delivered, but >I'm also sympathetic to the "keep the wire copy" argument, and a little >worried because of the abovementioned failures; does anyone else run it >through procmail? Are you happy with your experience of same? I've been using

Re: [Nmh-workers] Maybe time for a new release?

Hi Ken, > Norm wrote: > > The bulk of the non-spam mail I receive still has a utf-8 or a > > quotedPrintable part. I would like to apply UNIX text processing > > tools (grep, wc, sort, uniq, perl, etc) to these messages. > > I ... think the latest release makes that easy as well? Does Norm have

Re: [Nmh-workers] Maybe time for a new release?

Ken> I ... think the latest release makes that easy as well? It sounds Ken> like the only thing lacking from 1.6 in this area is documentation. Yes, seems so; I guess I'd just like a "best practice" section in the mhfixmsg man page which shows (for example) a recommended command line invocation

Re: [Nmh-workers] Maybe time for a new release?

>The bulk of the non-spam mail I receive still has a utf-8 or a quotedPrintable >part. I would like to apply UNIX text processing tools (grep, wc, sort, uniq, >perl, etc) to these messages. It would be nice if the next release made that >reasonably easily possible. I ... think the latest release

Re: [Nmh-workers] Maybe time for a new release?

David Levine writes: >Norm wrote: > >> David Levine writes: >> >> >Translate text/plain parts to UTF-8 To translate all text/plain parts in >> >the current message to UTF-8, in addition to all of the default >> >transformations: >> > >> >mhfixmsg -textcharset

Re: [Nmh-workers] Maybe time for a new release?

>How do I translate, to utf-8, all parts of a message, >which can be reasonably translated to utf-8? The first such part? David gave you a good answer, but to expand on it a bit ... Since not all Unicode codepoints are guaranteed to be represented as UTF-8 in text/html, you can't really convert

Re: [Nmh-workers] Future directions for nmh

Andy Bradford wrote: What's wrong with the way nmh does it today? Maildir is certainly superior for some of the reasons detailed below, but nmh's Mail store isn't very far off: http://cr.yp.to/proto/maildir.html some of us have converted to Maildir, but we miss MH's CLI

Re: [Nmh-workers] Maybe time for a new release?

>I can freshen up the branch. Did anyone ever review it? Should I merge it >as is? We should settle the api key management issue too. I looked at it, but I cannot say that I reviewed it; every time I sat down to really study it, I got lost in the whole OAUTH maze, then I got busy, it fell onto

Re: [Nmh-workers] Maybe time for a new release?

Norm wrote: > David Levine writes: > > >Translate text/plain parts to UTF-8 > >To translate all text/plain parts in the current message to UTF-8, in > >addition to all of the default transformations: > > > >mhfixmsg -textcharset utf-8 > > How do I translate, to utf-8, all parts

Re: [Nmh-workers] Maybe time for a new release?

Eric wrote: > I can freshen up the branch. Did anyone ever review it? Should I merge it > as is? We should settle the api key management issue too. I looked at it, but not even close to review. How about leaving it on the branch and we'll look it at there. I really do want to use it, just

Re: [Nmh-workers] Maybe time for a new release?

David Levine writes: >Norm wrote: > >> Maybe Contributions should have a tutorial script or two which >> illustrate good ways to do that? > >How about adding this to the man page? > >EXAMPLES >Basic usage >To run mhfixmsg on the current message in the current folder, with

Re: [Nmh-workers] Maybe time for a new release?

I can freshen up the branch. Did anyone ever review it? Should I merge it as is? We should settle the api key management issue too. Thanks. On Tue, Mar 8, 2016, 4:25 PM Ken Hornstein wrote: > I've been itching to do some MIME refactoring, and by "refactoring" I > mean

Re: [Nmh-workers] Future directions for nmh

Thus said Ken Hornstein on Wed, 09 Mar 2016 10:44:55 -0500: > I am saying that we have people who want to use the nmh tools with > both IMAP and Maildir mailstores. So making the nmh tools work with > those mailstores would be useful. Oh, I misunderstood. So part of my last email is no

Re: [Nmh-workers] Future directions for nmh

Thus said Ken Hornstein on Wed, 09 Mar 2016 10:18:04 -0500: > 1) I do not think converting and storing incoming messages as UTF-8 is >wise. In terms of just simplicity alone I think messages should be >stored (somewhere) in their on-the-wire format; I too agree with this position. The