I’ve noticed a small issue with my email client for quite some time now where composing a new email will have several blank lines by default.

It’s not too much of an issue to simply delete them but hey, maybe no one had pointed this out before! So I filed a bug report only to get this response… basically it’s not a bug, its a feature!

    • Trarmp@feddit.nl
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      🤮

      This reminds me of text editor that leave half a screen of ‘wiggle room’ when scrolling down. Absolutely hate it, and if I can’t turn it off, I won’t use the text editor.

  • CompassRed@discuss.tchncs.de
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    It’s not a bug just because the software doesn’t conform to your personal preferences. You’re asking for what would be considered an enhancement - not a bug fix.

      • CompassRed@discuss.tchncs.de
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        I don’t know the reason. I think not having the extra blank lines would be better, but it works just fine as is - even the post admits this much. That’s why it’s an enhancement. It’s possible for software to be functional and consistent and still have room for improvement - that doesn’t mean there is a bug.

    • stifle867@programming.devOP
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      It’s not about preference. It’s about what every single other email client does, including their own on different platforms, and this is even fixed in their upcoming beta of this same app.

      • CompassRed@discuss.tchncs.de
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        My point is that someone made the decision for it to do that and that the software works just fine as is. It’s not a bug, it’s just a weird quirk. The fact that they made the enhancement you requested doesn’t make the old behavior buggy. Your post title said “it’s not a bug, it’s a feature!”, but the behavior you reported is not accurately classified as a bug.