Re: [Nmh-workers] Changes to forw(1)

Date:14 Oct 2016 13:46:58 -0600 From:"Andy Bradford" Message-ID: <20161014134658.23137.qm...@angmar.bradfordfamily.org> | Why? What's wrong with "X-"? If the intent of RFC 6648 is to do away | with any special interpretation of "X-" in

Re: [Nmh-workers] I see nmh is now available in epel repo for RHEL, Scientific Linux and CentOS

David Levine writes: > Jón wrote: > >> This morning I got a notification from the package manager that >> a new version of nmh was available. This was a nice surprise as >> hitherto I had built my own rpms for nmh (and was rather behind >> the times). So now upgraded to 1.6 >>

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

>:-) Through a cunning bit of social engineering the other day, I did >apparently gain access to nmh's git repository. Is there anything that >documents conventions in using it for the project, e.g. whether to check >in directly on master or use a branch? I think David covered the (lack of

Re: [Nmh-workers] When a message goes only to me, as a cc

>But it seems to me that a lot of the complexity comes from nmh not only >accepting the (odd, daft, brain-damaged) GNU convention of allowing >adjectives after the nouns, but producing such an argv itself. If >postproc knew that argv[argc-1] was the draft file, given argv>1, then >it wouldn't

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Hi, David wrote: > See docs/README.developers. Thanks, that helped quite a bit. I've pushed a trivial fix to master. If I've done anything wrong, e.g. not configured my ID properly, then let me know. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy

Re: [Nmh-workers] When a message goes only to me, as a cc

Hi, Norm wrote: > Would you be willing to tell me how, in such a script, I could detect > the presence or absence of a specific header, say "Exception: norm"? So, thanks to the other replies, Norm's happy taking Ken's http://lists.nongnu.org/archive/html/nmh-workers/2016-10/txthpshEQcPNr.txt and

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Ralph wrote: > Thanks, that helped quite a bit. I've pushed a trivial fix to master. > If I've done anything wrong, e.g. not configured my ID properly, then > let me know. Looks fine. One thing that we should add to README.developers, the buildbot results are available at

Re: [Nmh-workers] When a message goes only to me, as a cc

Norm wrote: > Turns out it is documented, though not in a very straightforward place. > man mh_profile, under postproc. I'm in documentation mode, so if you have a suggestion on where to add a link to that postproc entry, please let me know. Where is the first place that you looked? post(8),

Re: [Nmh-workers] When a message goes only to me, as a cc

n...@dad.org wrote: > >I think the simplest thing to do would be to write a custom postproc > >and use it to interrogate the draft (using scan(1)) to make sure it was > >the way you want. Like if the To: line was blank, exit with a sensible > >error message. If you were happy with it, call

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Ralph wrote: > 1.6's mhshow(1) says Might Ken's commit adfed5f72bc07ac7de8dfc62188338d4d4f25a38 have fixed this? > I took a look at mhshowsbr.c's convert_charset() and I think it's > failing to handle an EINVAL return. That commit adds handling of EINVAL and EISLEQ, relevant portion of the

Re: [Nmh-workers] When a message goes only to me, as a cc

>I think the simplest thing to do would be to write a custom postproc >and use it to interrogate the draft (using scan(1)) to make sure it was >the way you want. Like if the To: line was blank, exit with a sensible >error message. If you were happy with it, call the real post. > >I've attached

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Ralph wrote: > Hi David, > > :-) Through a cunning bit of social engineering the other day, I don't want to know :-) > I did apparently gain access to nmh's git repository. Is there > anything that documents conventions in using it for the project, > e.g. whether to check in directly on

[Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Hi, I got an email recently, probably spam, its charset is gb2312. $ mhlist msg part type/subtype size description 8032 text/plain 10K charset="gb2312" $ 1.6's mhshow(1) says mhshow: unable to convert character set to

Re: [Nmh-workers] nmh documentation

Norm wrote: > But I wonder how much additional clarification is wise. Perhaps nmh > documentation is reaching, or has reached, the law of diminishing returns. The > more man pages that are added and the longer man pages become, the harder it > will be to find something, and the less likely it

[Nmh-workers] nmh documentation

David Levine writes: >Norm wrote: > >> Turns out it is documented, though not in a very straightforward place. >> man mh_profile, under postproc. > >I'm in documentation mode, so if you have a suggestion on where to add >a link to that postproc entry, please let me know. Where

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

>> 1.6's mhshow(1) says > >Might Ken's commit adfed5f72bc07ac7de8dfc62188338d4d4f25a38 >have fixed this? I think our generic assumption is that utf8 is the only multibyte sequence we have to deal with. Although I guess that really only matters if we get an EILSEQ and we're substituting a '?'.

Re: [Nmh-workers] When a message goes only to me, as a cc

Paul Fox writes: >n...@dad.org wrote: >> >I think the simplest thing to do would be to write a custom postproc >> >and use it to interrogate the draft (using scan(1)) to make sure it was >> >the way you want. Like if the To: line was blank, exit with a sensible >>

Re: [Nmh-workers] When a message goes only to me, as a cc

n...@dad.org wrote: > Paul Fox writes: > >n...@dad.org wrote: > >> >I think the simplest thing to do would be to write a custom postproc > >> >and use it to interrogate the draft (using scan(1)) to make sure it was > >> >the way you want. Like if the To: line was

Re: [Nmh-workers] Changes to forw(1)

Hello Ralph, this likely goes to you in private only (via News) Ralph Corderoy wrote: |kre wrote: |> Rather, I usually delete [X-Mailer] as I consider it no-one else's |> business which software I use | |Yes, I'd want to turn it off from that point of view too. I

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Hi again, > 1.6's mhshow(1) says > > mhshow: unable to convert character set to gb2312, continuing... I meant to draw attention to that. It was converting *from* gb2312 (to UTF-8). -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ___

Re: [Nmh-workers] When a message goes only to me, as a cc

Ken Hornstein writes: >I think you mean '-whom'. And yes, that is true. And yes, it's not >documented either; I learned that the hard way. Turns out it is documented, though not in a very straightforward place. man mh_profile, under postproc. Norman Shapiro

Re: [Nmh-workers] Changes to forw(1)

Hi Ken > I admit I am not clear where Ralph stands on this particular issue; > perhaps the Marmite shortage is affecting things :-) Marmite's basic ingredient is yeast sludge, a waste product from brewing beer. Give me the beer. It's solely produced in Burton, which used to have a large

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Hi David, > Might Ken's commit adfed5f72bc07ac7de8dfc62188338d4d4f25a38 have fixed > this? Yes, indeed. I get identical output from iconv(1) and mhshow(1) with the function from http://git.savannah.gnu.org/cgit/nmh.git/tree/uip/mhshowsbr.c. > + if (errno == EINVAL) { > + /*

Re: [Nmh-workers] When a message goes only to me, as a cc

Paul Fox writes: >n...@dad.org wrote: >> Paul Fox writes: >> >n...@dad.org wrote: >> >> >I think the simplest thing to do would be to write a custom postproc >> >> >and use it to interrogate the draft (using scan(1)) to make sure it was >> >>

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Ralph wrote: > > 1.6's mhshow(1) says > > > > mhshow: unable to convert character set to gb2312, continuing... > > I meant to draw attention to that. It was converting *from* gb2312 (to > UTF-8). Fixed, thanks. David ___ Nmh-workers mailing list

Re: [Nmh-workers] Changes to forw(1)

Hi Paul, > > No, I mean "Subjct: Nice to see you again" isn't embarassing; I > > always intended they'd see the header's value. "Bc: myboss, > > yourboss", is. And "Atach: /home/ralph/pita-client/foo" is as > > normally they'd only see "foo". > > but there's no solution, to this, right? we

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Hi David, > Great! We'll get you to the bleeding edge yet. :-) Through a cunning bit of social engineering the other day, I did apparently gain access to nmh's git repository. Is there anything that documents conventions in using it for the project, e.g. whether to check in directly on master

Re: [Nmh-workers] Changes to forw(1)

Hi, kre wrote: > Rather, I usually delete [X-Mailer] as I consider it no-one else's > business which software I use Yes, I'd want to turn it off from that point of view too. I use mail(1) for short internal emails, and here it's provided by package s-nail which had a series of different

Re: [Nmh-workers] mhshow(1) iconv(3) Bug if Multibyte Straddles Buffer End.

Ralph wrote: > Hi David, > > > Might Ken's commit adfed5f72bc07ac7de8dfc62188338d4d4f25a38 have fixed > > this? > > Yes, indeed. Great! We'll get you to the bleeding edge yet. > IOW, it seeks to 4Ki and reads 4Ki - 1 so it's left in the right place > to read the one byte, that we already have,