[Nmh-workers] 1.7's putnum drops data if too close to end of line?

[Tom Lane]

I use a scan format that ends with

%(decode{subject}) (%(putnum(size)))

(all the previous output is fixed-width columns, so not interesting here).
As of 1.7 I'm seeing that the size data drops out if it would run off the
end of the available space.  For example, an excerpt from "scan -width
100" output is

89716  12/01 16:53  Alvaro Herrera             hack  Re: [HACKERS] Custom 
compression methods (4659)
89717  12/02 20:27  Jeff Janes                 perf  Re: Bitmap scan is 
undercosted? (12398)
89718  12/02 21:52  Oleg Bartunov              hack  Re: [HACKERS] Custom 
compression methods ()
89720  12/02 22:27  chenhj                     hack  Re:Re: [HACKERS] 
[PATCH]make pg_rewind to not c
89721  12/02 23:04  Justin Pryzby              perf  Re: Bitmap scan is 
undercosted? - boolean corre
89722  12/03 01:21  Pavel Stehule              hack  pg_dumpall -r -c try to 
drop user postgres ()

What I'd expect to happen, and what did happen before 1.7, is that the
size information would be there and would just be truncated if it didn't
fit in the available output width.  For instance, the last message shown
above has size 4467 so it ought to look like

89722  12/03 01:21  Pavel Stehule              hack  pg_dumpall -r -c try to 
drop user postgres (446

This might be related to the issue Ken Hornstein reported in
http://lists.nongnu.org/archive/html/nmh-workers/2017-11/msg00053.html

                        regards, tom lane