Re: [Nmh-workers] Poor behavior of %(putaddr)

2012-01-14 Thread Ken Hornstein
>mh-format says this: > > When a function or component escape is interpreted and the result > will be immediately printed, an optional field width can be > specified to print the field in exactly a given number of > characters. > >Note the text, "optional field width." Thus,

Re: [Nmh-workers] Loop support in mh-format?

2012-01-14 Thread Ken Hornstein
>> But how would you exit the loop, that's what I don't understand. > >Me neither. I was hoping a caller that bothered to check for a non-NULL >return would explain but didn't notice one. Is JLR still around? He posted to nmh-workers a year ago, but I don't know how much he keeps up with what's

Re: [Nmh-workers] Poor behavior of %(putaddr)

2012-01-14 Thread Bill Wohler
Ken Hornstein writes: > Earl Hood mentioned that he was running into problems with "repl" > hanging, and I ran into the same thing as well during some testing > here, so I went and tracked down the problem. Basically, it boils > down to the use of %(putaddr) when "num" is zero. > > %(putaddr) us

Re: [Nmh-workers] Loop support in mh-format?

2012-01-14 Thread Ralph Corderoy
Hi Ken, > the idea was that if fmt_scan() returned non-NULL, you'd call > fmt_scan() again and you'd pick up after the FT_DONE instruction? That's my understanding. > But how would you exit the loop, that's what I don't understand. Me neither. I was hoping a caller that bothered to check for a