On 2017-10-17 20:38, Pete Forman wrote: > Thomas Jollans <t...@tjol.eu> writes: > >> On 16/10/17 20:02, Pete Forman wrote: >>> Thomas Jollans <t...@tjol.eu> writes: >>> >>>> On 2017-10-16 08:48, Pete Forman wrote: >>>>> Andrew Z <form...@gmail.com> writes: >>>>> >>>>>> hmm. i did do that. maybe just a delay. >>>>>> I'll see how it will go tomorrow then. Thank you gents. >>>>>> >>>>>> On Mon, Oct 16, 2017 at 12:30 AM, Chris Angelico <ros...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> On Mon, Oct 16, 2017 at 3:19 PM, Andrew Z <form...@gmail.com> wrote: >>>>>>>> Michael, that's what i use too - gmail. But i get the digest only >>>>>>>> and can't really reply that way. i was hoping to get the >>>>>>>> mail.python.org list.... >>>>>>> >>>>>>> Turn off digests then. Easy! >>>>> >>>>> If you do stick with a digest then check your newsreader for a feature >>>>> to expand it. Then you can read and reply as if you were getting >>>>> individual posts. >>>>> >>>> That exists? How does it work? >>> >>> The Gnus newsreader in Emacs allows you to type C-d on a digest to run >>> gnus-summary-enter-digest-group. That then behaves the same as if you >>> opened any other summary such as a regular Usenet group. >>> >> >> Does it set the References header correctly when replying? > > Sorry, I am not in a position to test. The only digest I subscribe to is > comp.risks. The only messsage id in that is a single one for the whole > digest. Each article only has date, subject and from headers. You would > need to look inside a Python digest to see if it carries more headers > for the articles. If they are not present then they cannot be used when > composing a reply. >
I see. I've never subscribed to anything as a digest so I don't really know what they look like, but judging from https://mail.python.org/pipermail/python-list/2017-October/727421.html (section of the digest quoted at the bottom) it *could* work. -- Thomas Jollans -- https://mail.python.org/mailman/listinfo/python-list
