unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: [PATCH] view: fix unclosed parentheses after `raw' link
Date: Fri, 30 Aug 2024 20:36:35 +0000	[thread overview]
Message-ID: <20240830203635.M599683@dcvr> (raw)
In-Reply-To: <20240830-crystal-active-dingo-03bfbd@lemur>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> This is completely inconsequential, but it's driving my OCD into a bad place.
> There is a missing paren in the header of each message:
> 
> 	* Committing crimes with NTFS-3G
> 	@ 2024-08-29 20:43 XXXXXXXXX
> 	  2024-08-30  0:47 ` XXXXXXXXXXXX
> 					   ` (2 more replies)
> 	  0 siblings, 3 replies; 9+ messages in thread
> 	From: XXXXXXX @ 2024-08-29 20:43 UTC (permalink / raw
>                                                          ^ :(
> 	  To: git
> 
> It can be seen live here:
> https://lore.kernel.org/all/fe9d19fa-661d-4358-aa0a-ea419c419266@gaijin.team/T/#t
> 
> Any way to get it fixed? :)

Not OCD at all and definitely a bug, thanks for the report :>

------8<----
Subject: [PATCH] view: fix unclosed parentheses after `raw' link

This formatting error was accidentally introduced while
converting a `qq{}' concatenation to a `say' statement.  Re-add
the `)'.   While we're at it, switch to a `print' statement
since we use a string literal anyways and `say' would require an
extra global variable lookup at runtime.

Fixes: 18f41f5af397f903 (www: replace *eml_entry with *emit_eml, 2024-07-07)
Reported-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Link: https://public-inbox.org/meta/20240830-crystal-active-dingo-03bfbd@lemur/
---
 lib/PublicInbox/View.pm | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lib/PublicInbox/View.pm b/lib/PublicInbox/View.pm
index ce8fa865..131727fc 100644
--- a/lib/PublicInbox/View.pm
+++ b/lib/PublicInbox/View.pm
@@ -270,9 +270,9 @@ sub emit_eml ($$) {
 	obfuscate_addrs($obfs_ibx, $from) if $obfs_ibx;
 	my $upfx = $ctx->{-upfx};
 	my $mhref = $upfx . mid_href($mid_raw) . '/';
-	say $zfh 'From: ', $from, ' @ ', fmt_ts($ds), qq[ UTC (<a\nhref="],
+	print $zfh 'From: ', $from, ' @ ', fmt_ts($ds), qq[ UTC (<a\nhref="],
 			$mhref, qq[">permalink</a> / <a\nhref="],
-			$mhref, 'raw">raw</a>';
+			$mhref, qq[raw">raw</a>)\n];
 	{
 		my ($to, $tlen) = to_cc_html($ctx, $eml, 'To', $t);
 		my ($cc, $clen) = to_cc_html($ctx, $eml, 'Cc', $t);

  reply	other threads:[~2024-08-30 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30 19:37 OCD request: missing paren in web view Konstantin Ryabitsev
2024-08-30 20:36 ` Eric Wong [this message]
2024-08-30 21:31   ` [PATCH] view: fix unclosed parentheses after `raw' link Konstantin Ryabitsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240830203635.M599683@dcvr \
    --to=e@80x24.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).