diff options
| author | klm | 1998-11-22 01:34:15 +0000 |
|---|---|---|
| committer | klm | 1998-11-22 01:34:15 +0000 |
| commit | 1c4827ff8fc6425e82ac2ee519e92e0258179f3c (patch) | |
| tree | 611759f3ff7ab6b7c3714485c70352cdf30ec960 /Mailman/HTMLFormatter.py | |
| parent | 01c00d8bacf9e2bdfb512944236063d8c967b1f4 (diff) | |
| download | mailman-1c4827ff8fc6425e82ac2ee519e92e0258179f3c.tar.gz mailman-1c4827ff8fc6425e82ac2ee519e92e0258179f3c.tar.zst mailman-1c4827ff8fc6425e82ac2ee519e92e0258179f3c.zip | |
Here's two drastic policy-level changes to the archive mechanism.
First of all, i'm setting the default message archive style to
preserve horizontal whitespace, use <pre>, instead of putting a <br>
at the beginning of every line.
More deeply, i'm inhibiting all completely-uppercase variables from
being included in the pickled settings for the list. As with the
VERBOSE problem i addressed in my last checkin, changes to one of the
class default settings at any time *after* the archive object state
was resurrected would be reinstated thence forward - overriding the
defaults, and any other settings. This is not a good interface for
setting options - and i'm not really offering an alternative, other
than making the defaults come back the next time the list is
reinstated, rather than preserving the changes. We need to resolve
this - i suppose with an interface that distinguishes permanent from
temporary settings.
In general i've changed the defaults so they preserve more of the
structure of the postings (and included very brief comments presenting
what i could glean of the settings from the code - this code here does
not seem to have been written to be understood).
Diffstat (limited to 'Mailman/HTMLFormatter.py')
0 files changed, 0 insertions, 0 deletions
