FAQ
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.

Search Discussions

  • Mark Sapiro at Jun 10, 2006 at 11:50 pm

    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, 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 next links are actually in the HTML
    message file, and they are previous and next in thread regardless of
    how you got to the message.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Brad Knowles at Jun 11, 2006 at 2:13 am

    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 next links are actually in the HTML
    message file, and they are previous and next in thread regardless of
    how you got to the message.
    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.

    --
    Brad Knowles, <brad at stop.mail-abuse.org>

    "Those who would give up essential Liberty, to purchase a little
    temporary Safety, deserve neither Liberty nor Safety."

    -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
    Assembly to the Governor, November 11, 1755

    LOPSA member since December 2005. See <http://www.lopsa.org/>.
  • Mark Sapiro at Jun 11, 2006 at 3:06 am

    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 wonder about the actual appearance.
    Here's an example of the current

    # Previous message: [Mailman-Users] Mailman Delivery Issue
    # Next message: [Mailman-Users] Members list settings
    # Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Brad seems to be suggesting something like

    # Previous message: [Mailman-Users] Mailman Delivery Issue
    # Next message: [Mailman-Users] Members list settings
    (by thread)
    # Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    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 ]

    Any other thoughts/examples/opinions?

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Jim Popovitch at Jun 11, 2006 at 3:19 am

    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.

    -Jim P.
  • Dragon at Jun 11, 2006 at 6:59 pm
    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 ] [ thread ] [ subject ] [ author ]
    This example makes sense to me.
    ---------------- End original message. ---------------------

    And to me, it is clear and concise. It's also what I thought Brad
    meant when he proposed it.

    Dragon

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  • Brad Knowles at Jun 11, 2006 at 8:46 am

    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 ]

    Any other thoughts/examples/opinions?
    Now that I've seen the options, I like your idea best.

    --
    Brad Knowles, <brad at stop.mail-abuse.org>

    "Those who would give up essential Liberty, to purchase a little
    temporary Safety, deserve neither Liberty nor Safety."

    -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
    Assembly to the Governor, November 11, 1755

    LOPSA member since December 2005. See <http://www.lopsa.org/>.
  • Mark Sapiro at Jun 11, 2006 at 3:45 pm

    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 ] [ subject ] [ author ]

    Any other thoughts/examples/opinions?
    Now that I've seen the options, I like your idea best.

    It seems unanimous so I've committed the change in the Subversion trunk
    for Mailman 2.2.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Jim Popovitch at Jun 11, 2006 at 10:17 pm

    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
    # Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Any other thoughts/examples/opinions?
    Now that I've seen the options, I like your idea best.

    It seems unanimous so I've committed the change in the Subversion trunk
    for Mailman 2.2.
    Thanks Mark, Brad too for his input.

    Question: Where can I make this change today to MM 2.1.8?

    Thx,

    -Jim P.
  • Mark Sapiro at Jun 11, 2006 at 11:50 pm

    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 = ('<LINK REL="Previous" HREF="%s">'
    % (url_quote(self.prev.filename)))
    - prev_wsubj = ('<LI>' + _('Previous message:') +
    + prev_wsubj = ('<LI>' + _('Previous message (by thread):') +
    ' <A HREF="%s">%s\n</A></li>'
    % (url_quote(self.prev.filename),
    self.quote(subject)))
    @@ -515,7 +515,7 @@
    subject = self._get_subject_enc(self.next)
    next = ('<LINK REL="Next" HREF="%s">'
    % (url_quote(self.next.filename)))
    - next_wsubj = ('<LI>' + _('Next message:') +
    + next_wsubj = ('<LI>' + _('Next message (by thread):') +
    ' <A HREF="%s">%s\n</A></li>'
    % (url_quote(self.next.filename),
    self.quote(subject)))


    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedJun 10, '06 at 10:39p
activeJun 11, '06 at 11:50p
posts10
users4
websitelist.org

People

Translate

site design / logo © 2022 Grokbase