diff options
| author | Eric Wong <e@80x24.org> | 2016-04-16 18:46:35 +0000 |
|---|---|---|
| committer | Eric Wong <e@80x24.org> | 2016-04-16 18:46:35 +0000 |
| commit | 2f8d30432668e0cf17fac08637fecf66cf4e07ac (patch) | |
| tree | 5b2d452b453fc209a39bb779ccd9c275f364c8b1 /lib | |
| parent | 11ae07b591728a76d03493432dac9bc15299c446 (diff) | |
| download | public-inbox-2f8d30432668e0cf17fac08637fecf66cf4e07ac.tar.gz | |
Allowing readers new to a topic to follow in chronological order probably makes the most sense. Reverse chronological order may reduce scrolling (e.g. log view); but nearly all non-threaded conversation displays seem to be chronological so perhaps there's a good reason for that.
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/PublicInbox/View.pm | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/PublicInbox/View.pm b/lib/PublicInbox/View.pm index f07979e9..36df7ead 100644 --- a/lib/PublicInbox/View.pm +++ b/lib/PublicInbox/View.pm @@ -174,10 +174,10 @@ sub thread_html { sub emit_thread_html { my ($res, $ctx, $foot, $srch) = @_; my $mid = $ctx->{mid}; - my $msgs = load_results($srch->get_thread($mid)); + my $flat = $ctx->{flat}; + my $msgs = load_results($srch->get_thread($mid, { asc => $flat })); my $nr = scalar @$msgs; return missing_thread($res, $ctx) if $nr == 0; - my $flat = $ctx->{flat}; my $seen = {}; my $state = { res => $res, |