about summary refs log tree commit homepage
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2015-08-30 01:51:22 +0000
committerEric Wong <e@80x24.org>2015-08-30 01:54:00 +0000
commit2b3233ce3b309279ee3df8b99a471aa2e8c435e3 (patch)
treeb912df9bb94bec46d5920adf98a8422da1e0ce30
parent05fecbc7f61c9ff9ec44e8c74c1fe23cac0579a5 (diff)
downloadpublic-inbox-2b3233ce3b309279ee3df8b99a471aa2e8c435e3.tar.gz
We're already inside the thread, and our thread summary inside
/m/$MESSAGE_ID/ is already sufficient got navigate back to the
/t/$MESSAGE_ID/ page.  So I think it's sufficient to keep the
/t/$MESSAGE_ID/ page lighter with fewer links and avoid
introducing strange terminology.

In contrast, "permalink" is relatively well-known and
not an alien term to readers:

	https://en.wikipedia.org/wiki/Permalink
-rw-r--r--lib/PublicInbox/View.pm10
1 files changed, 1 insertions, 9 deletions
diff --git a/lib/PublicInbox/View.pm b/lib/PublicInbox/View.pm
index 7cac7851..3ee67902 100644
--- a/lib/PublicInbox/View.pm
+++ b/lib/PublicInbox/View.pm
@@ -74,13 +74,10 @@ sub index_entry {
         my $path = $root_anchor ? '../../' : '';
         my $href = $mid->as_href;
         my $irt = $header_obj->header('In-Reply-To');
-        my ($anchor_idx, $anchor, $t_anchor);
+        my ($anchor_idx, $anchor);
         if (defined $irt) {
                 $anchor_idx = anchor_for($irt);
                 $anchor = $seen->{$anchor_idx};
-                $t_anchor = T_ANCHOR;
-        } else {
-                $t_anchor = '';
         }
         if ($srch) {
                 $subj = "<a\nhref=\"${path}t/$href/#u\">$subj</a>";
@@ -134,11 +131,6 @@ sub index_entry {
                 $rv .= " <a\nhref=\"$anchor\">parent</a>";
         }
 
-        if ($srch) {
-                $rv .= " <a\nhref=\"${path}t/$href/$t_anchor\">" .
-                       "threadlink</a>";
-        }
-
         $fh->write($rv .= '</pre></td></tr></table>');
 }