Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header

2016-09-04 Thread Ben Finney
On Sun, 2016-09-04 16:44 -0700, Don Armstrong wrote: > On Sun, 04 Sep 2016, Ben Finney wrote: > > The ‘debbugs’ server has evidently retrieved a completely different > > text, some “Received” field from the message header. This fails to > > meet the behaviour described in the

Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header

2016-09-04 Thread Don Armstrong
On Sun, 04 Sep 2016, Ben Finney wrote: > The ‘debbugs’ server has evidently retrieved a completely different > text, some “Received” field from the message header. This fails to > meet the behaviour described in the documentation. Hrm; yeah, that was working in the past, and what you saw now is

Bug#836613: debbugs: specifying 0 (“current message”) causes ‘summary’ to attempt to parse message header

2016-09-04 Thread Ben Finney
Package: debbugs Severity: normal The attached response came from ‘debbugs’ when I sent a message that contains a command “summary -1 0”. According to the documentation for that command: The first