Jim Popovitch wrote:
>
>Question: Where can I make this change today to MM 2.1.8?
Mailman/Archiver/HyperArch.py
--- HyperArch.py(revision 7893)
+++ HyperArch.py(working copy)
@@ -493,7 +493,7 @@
subject = self._get_subject_enc(self.prev)
prev = (''
Mark Sapiro wrote:
> Brad Knowles wrote:
>
>> At 8:06 PM -0700 2006-06-10, Mark Sapiro wrote:
>>
>>> I think I prefer something like
>>>
>>> # Previous message (by thread): [Mailman-Users] Mailman Delivery Issue
>>> # Next message (by thread): [Mailman-Users] Members list settings
>>> # Messag
Jim Popovitch sent the message below at 08:19 PM 6/10/2006:
>Mark Sapiro wrote:
> > I think I prefer something like
> >
> > # Previous message (by thread): [Mailman-Users] Mailman Delivery Issue
> > # Next message (by thread): [Mailman-Users] Members list settings
> > # Messages sorted by: [ date
Brad Knowles wrote:
>At 8:06 PM -0700 2006-06-10, Mark Sapiro wrote:
>
>> I think I prefer something like
>>
>> # Previous message (by thread): [Mailman-Users] Mailman Delivery Issue
>> # Next message (by thread): [Mailman-Users] Members list settings
>> # Messages sorted by: [ date ] [ thread
At 8:06 PM -0700 2006-06-10, Mark Sapiro wrote:
> I think I prefer something like
>
> # Previous message (by thread): [Mailman-Users] Mailman Delivery Issue
> # Next message (by thread): [Mailman-Users] Members list settings
> # Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>
Mark Sapiro wrote:
> I think I prefer something like
>
> # Previous message (by thread): [Mailman-Users] Mailman Delivery Issue
> # Next message (by thread): [Mailman-Users] Members list settings
> # Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
This example makes sense to me.
Brad Knowles wrote:
>
> Ahh. In which case, we should probably change the tag info to
>indicate that the previous and next message are by thread. Having a
>"(by thread)" comment after the "previous" and "next" links would
>probably be sufficient.
I'm ready to make the change, but I won
At 4:50 PM -0700 2006-06-10, Mark Sapiro wrote:
> Yes. This is the way it works. There are periodic (monthly) index files
> in thread, subject, author and date order, but there is only one HTML
> file per message and that one file is linked from all four index
> files, but the previous and nex
Jim Popovitch wrote:
>When viewing a pipermail (MM 2.1.8) list archive by Date, is it normal
>for "Previous message" and "Next message" to navigate to the previous
>and next by Thread rather than by Date?
Yes. This is the way it works. There are periodic (monthly) index files
in thread, subjec
When viewing a pipermail (MM 2.1.8) list archive by Date, is it normal
for "Previous message" and "Next message" to navigate to the previous
and next by Thread rather than by Date?
-Jim P.
--
Mailman-Users mailing list
Mailman-Users@python.org
10 matches
Mail list logo
