[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Nmh-workers] scan -width behaves oddly in 1.5RC3
From: |
Tom Lane |
Subject: |
[Nmh-workers] scan -width behaves oddly in 1.5RC3 |
Date: |
Wed, 06 Jun 2012 12:18:51 -0400 |
I use scan with this scan form:
%5(msg)%<(cur)+%| %>%<{replied}-%|%<{encrypted}E%| %>%>\
%(date2local{date})\
%02(mon{date})/%02(mday{date}) %02(hour{date}):%02(min{date})\
%<{date} %|*%> \
%<(mymbox{from})=>%23(decode(friendly{to}))%|%25(decode(friendly{from}))%> \
%(decode{subject}) (%(putnum(size)))
(I forget the provenance of this thing, but it's likely a modified
version of what exmh supplies.) In addition to the -form argument, exmh
sticks in a -width argument. That's always behaved as expected with nmh
1.0.4, but something weird is happening with the final putnum call in
1.5RC3: sometimes, when the line is almost full, I see "()" at the end,
where I would expect to see "(" and a digit or two, the rest being
suppressed by the width limit. Here is an example:
$ scan -width 94 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix socket
$ scan -width 95 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix sockets
$ scan -width 96 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix sockets
$ scan -width 97 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix sockets (
$ scan -width 98 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix sockets ()
$ scan -width 99 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix sockets ()
$ scan -width 100 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix sockets ()
$ scan -width 101 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix sockets (3413
$ scan -width 102 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix sockets (3413)
$ scan -width 103 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix sockets (3413)
$ scan -width 104 81868
81868+ 06/06 09:50 Honza Horak [HACKERS] Ability to listen on
two unix sockets (3413)
(The -form argument is coming from .mh_profile, btw.)
It sorta looks like putnum has been taught not to put in any of the
number unless it will all fit, which to my mind is not an improvement;
it doesn't meet the principle of least astonishment anyway. Is this
intentional, or just a bug? If the latter, any suggestions where to
look to debug it?
regards, tom lane
- [Nmh-workers] scan -width behaves oddly in 1.5RC3,
Tom Lane <=
- Re: [Nmh-workers] scan -width behaves oddly in 1.5RC3, Ken Hornstein, 2012/06/06
- Re: [Nmh-workers] scan -width behaves oddly in 1.5RC3, Ken Hornstein, 2012/06/06
- Re: [Nmh-workers] scan -width behaves oddly in 1.5RC3, Tom Lane, 2012/06/06
- Re: [Nmh-workers] scan -width behaves oddly in 1.5RC3, Ken Hornstein, 2012/06/06
- Re: [Nmh-workers] scan -width behaves oddly in 1.5RC3, Tom Lane, 2012/06/06
- Re: [Nmh-workers] scan -width behaves oddly in 1.5RC3, Ken Hornstein, 2012/06/06
- Re: [Nmh-workers] scan -width behaves oddly in 1.5RC3, Tom Lane, 2012/06/06
- Re: [Nmh-workers] scan -width behaves oddly in 1.5RC3, Ken Hornstein, 2012/06/06
- Re: [Nmh-workers] scan -width behaves oddly in 1.5RC3, paul vixie, 2012/06/06
- Re: [Nmh-workers] scan -width behaves oddly in 1.5RC3, Ralph Corderoy, 2012/06/06