[PATCH 0/2] view: reply instruction tweaks

[PATCH 0/2] view: reply instruction tweaks

[Eric Wong]

It may be 2016, but top-posting still makes me cringe :<

Eric Wong (2):
      view: improve readability of msg_reply with here-doc
      view: reference posting style article on Wikipedia

 lib/PublicInbox/View.pm | 42 ++++++++++++++++++++++++++++--------------
 1 file changed, 28 insertions(+), 14 deletions(-)

[PATCH 1/2] view: improve readability of msg_reply with here-doc

[Eric Wong]

This should make formatting more apparent since we can rely
on <pre> semantics.
---
 lib/PublicInbox/View.pm | 36 ++++++++++++++++++++++--------------
 1 file changed, 22 insertions(+), 14 deletions(-)

diff --git a/lib/PublicInbox/View.pm b/lib/PublicInbox/View.pm
index 27dd155..9d48dfc 100644
--- a/lib/PublicInbox/View.pm
+++ b/lib/PublicInbox/View.pm
@@ -54,21 +54,29 @@ sub msg_reply {
 
 	my ($arg, $link) = mailto_arg_link($hdr);
 	push @$arg, '/path/to/YOUR_REPLY';
+	$arg = join(" \\\n    ", '', @$arg);
+	<<EOF
+<pre
+id=R>You may reply publically to <a
+href=#t>this message</a> via
+plain-text email using any one of the following methods:
 
-	"<pre\nid=R>".
-	"You may reply publically to <a\nhref=#t>this message</a> via\n".
-	"plain-text email using any one of the following methods:\n\n" .
-	"* Save the following mbox file, import it into your mail client,\n" .
-	"  and reply-to-all from there: <a\nhref=raw>mbox</a>\n\n" .
-	"* Reply to all the recipients using the <b>--to</b>, <b>--cc</b>,\n" .
-	"  and <b>--in-reply-to</b> switches of git-send-email(1):\n\n" .
-	"  git send-email \\\n    " .
-	join(" \\\n    ", @$arg ). "\n\n" .
-	qq(  <a\nhref="$se_url">$se_url</a>\n\n) .
-	"* If your mail client supports setting the <b>In-Reply-To</b>" .
-	" header\n  via mailto: links, try the " .
-	qq(<a\nhref="$link">mailto: link</a>\n) .
-	'</pre>';
+* Save the following mbox file, import it into your mail client,
+  and reply-to-all from there: <a
+href=raw>mbox</a>
+
+* Reply to all the recipients using the <b>--to</b>, <b>--cc</b>,
+  and <b>--in-reply-to</b> switches of git-send-email(1):
+
+  git send-email$arg
+
+  <a
+href="$se_url">$se_url</a>
+
+* If your mail client supports setting the <b>In-Reply-To</b> header
+  via mailto: links, try the <a
+href="$link">mailto: link</a></pre>
+EOF
 }
 
 sub in_reply_to {
-- 
EW

[PATCH 2/2] view: reference posting style article on Wikipedia

[Eric Wong]

Storage is precious when it is forever and distributed.

And public-inbox aims to not only end Eternal September(*),
but to build a world less-centralized than Usenet ever was:
forkable discussion groups

(*) https://en.wikipedia.org/wiki/Eternal_September
---
 lib/PublicInbox/View.pm | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/lib/PublicInbox/View.pm b/lib/PublicInbox/View.pm
index 9d48dfc..8487c2a 100644
--- a/lib/PublicInbox/View.pm
+++ b/lib/PublicInbox/View.pm
@@ -51,6 +51,8 @@ sub msg_reply {
 	my ($ctx, $hdr) = @_;
 	my $se_url =
 	 'https://kernel.org/pub/software/scm/git/docs/git-send-email.html';
+	my $p_url =
+	 'https://en.wikipedia.org/wiki/Posting_style#Interleaved_style';
 
 	my ($arg, $link) = mailto_arg_link($hdr);
 	push @$arg, '/path/to/YOUR_REPLY';
@@ -65,6 +67,10 @@ plain-text email using any one of the following methods:
   and reply-to-all from there: <a
 href=raw>mbox</a>
 
+  Avoid top-posting and favor interleaved quoting:
+  <a
+href="$p_url">$p_url</a>
+
 * Reply to all the recipients using the <b>--to</b>, <b>--cc</b>,
   and <b>--in-reply-to</b> switches of git-send-email(1):
 
-- 
EW