Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-7439

Pull request comment text box should use monospace font

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • None
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Pull request comments very frequently include a snippet of code, and these are quite difficult to format correctly when the text box in which the user has to type them doesn't use a monospace font. Given that code review is the primary purpose of pull request comments, the text box should use a monospace font.

            [BSERV-7439] Pull request comment text box should use monospace font

            Thanks for the suggestion Kelsey!

            In order to keep the comment interface appealing for the broader use case (ie not just code), it's unlikely we'd make the font monospace.

            However, we're considering a richer syntax aware editor interface which could make code block rendering more readable manner while entering comments.

            Roger Barnes (Inactive) added a comment - Thanks for the suggestion Kelsey! In order to keep the comment interface appealing for the broader use case (ie not just code), it's unlikely we'd make the font monospace. However, we're considering a richer syntax aware editor interface which could make code block rendering more readable manner while entering comments.

            Ah, sorry for the misunderstanding kelseyfrancis, I see what you mean now. I will reopen the feature request.

            Michael McGlynn (Inactive) added a comment - Ah, sorry for the misunderstanding kelseyfrancis , I see what you mean now. I will reopen the feature request.

            mmcglynn: My point was that typing in the code blocks is hard because the editor itself uses a variable-width font. The is especially annoying when reviewing languages where whitespace is significant. To clarify further: I'm familiar with how to get monospace text in Markdown; what I mean is that is difficult to actually type out the code that I'm trying to be monospace-formatted from inside a Stash pull request comment, because typing that code in Stash happens in a non-monospace font. That makes getting indentation right hard, and needlessly time consuming. Sure, I could do it in an external editor, but then it would be harder to look directly at the code I'm reviewing.

            Kelsey Francis added a comment - mmcglynn : My point was that typing in the code blocks is hard because the editor itself uses a variable-width font. The is especially annoying when reviewing languages where whitespace is significant. To clarify further: I'm familiar with how to get monospace text in Markdown; what I mean is that is difficult to actually type out the code that I'm trying to be monospace-formatted from inside a Stash pull request comment, because typing that code in Stash happens in a non-monospace font. That makes getting indentation right hard, and needlessly time consuming. Sure, I could do it in an external editor, but then it would be harder to look directly at the code I'm reviewing.

            Hi kelseyfrancis,
            If you wish to include a code snippet in your comment the best thing to do is use Markdown to include either inline code or a code block.

            Michael McGlynn (Inactive) added a comment - Hi kelseyfrancis , If you wish to include a code snippet in your comment the best thing to do is use Markdown to include either inline code or a code block .

              Unassigned Unassigned
              9886cafcfd09 Kelsey Francis
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: