public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-107297-4-raK7byGNX4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107297-4@http.gcc.gnu.org/bugzilla/>

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

--- 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 comments 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 the
benefits of markdown except for displaying preformatted code blocks? Embedded
links seem like spam fuel (currently we only hyperlink URLs and magic strings
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=1778863
New comments are indeed in proportional font, with embedded links, quote
blocks, and `code font` spans.

      parent reply	other threads:[~2022-10-19 11:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 13:30 [Bug other/107297] New: " jmuizelaar at mozilla dot com
2022-10-17 13:33 ` [Bug other/107297] " marxin at gcc dot gnu.org
2022-10-19  0:46 ` [Bug web/107297] " egallager at gcc dot gnu.org
2022-10-19  0:59 ` pinskia at gcc dot gnu.org
2022-10-19  1:01 ` pinskia at gcc dot gnu.org
2022-10-19  1:34 ` jmuizelaar at mozilla dot com
2022-10-19 10:51 ` redi at gcc dot gnu.org
2022-10-19 11:02 ` redi at gcc dot gnu.org [this message]

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

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

  git send-email \
    --in-reply-to=bug-107297-4-raK7byGNX4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).