From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 2BBFB385841A; Wed, 19 Oct 2022 11:02:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2BBFB385841A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1666177348;
	bh=h2IfPyrCJZv2/jtZx/xaWuRTspRU1hqDU1ONHNJ1YVo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=SgNcsDzocKvw0FY8F6C3zlJ3xTC0Wbji9FMJm7a5XR0xQHGVSwMA7iFBYkg5b0c5E
	 mcL1y8O5PMpIB7g12xAjZ5gkgdT2+1xLW+62mYwPWuKT2MYEaXrRAkii6hNYVgihDe
	 M2Z8RqR7VlO//c3oxOf6j2NSbfkgHYXy0naY1KkY=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/107297] Support markdown in bugzilla comments
Date: Wed, 19 Oct 2022 11:02:27 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107297-4-raK7byGNX4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107297-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107297-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107297

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> And many folks don't use markdown especially when they are used to plain
> text. C++ is the worst where < gets eaten up. This has been one of issues
> with github even.

Yes, automatically treating plain text as markdown when moving llvm bugs to
github was terrible. Retroactively altering the presentation of old comment=
s is
not acceptable. So let's assume old comments will not be affected in any way
(which is the case for BMO).

But there could be a checkbox (defaulting to off) to interpret the text as
markdown, so the commenter controls it. It would only affect new comments.

Since our bugzilla displays all comments in monospace font, what would be t=
he
benefits of markdown except for displaying preformatted code blocks? Embedd=
ed
links seem like spam fuel (currently we only hyperlink URLs and magic strin=
gs
like Bug 107297 comment 6 and git revisions). It seems like this is really a
request to support rich formatting, where markdown is just the means to an =
end,
not the actual goal.

I selected a recent BMO bug to see how it looks:
https://bugzilla.mozilla.org/show_bug.cgi?id=3D1778863
New comments are indeed in proportional font, with embedded links, quote
blocks, and `code font` spans.=