Sometimes you want to write something with broken lines and you write in the editor:

That’s right I’m Sokka
It’s pronounced with an Okka
Young Ladies, I rocked ya!

But it ends up looking like this:

That’s right I’m Sokka It’s pronounced with an Okka Young Ladies, I rocked ya!

The fix is to add two spaces between the final character and the carriage return.

I don’t understand what the problem is. CR should be easy enough to translate, and the users intentions are clearly confirmed because they’re looking right at what the expect it to look like when they hit submit.

Why does the user have to add two spaces? Why is the universe like this?

Edit: Holy Shit, look, I’m just an idiot typing text expecting WYSIWYG and I don’t see a good reason for why I’m not getting it other than that programmers lack theory of mind.

  • whaleross
    link
    fedilink
    arrow-up
    3
    ·
    6 days ago

    Because it is how the format is defined. There is nothing to fix. You write text in paragraphs by default and if you want it to be displayed in any other way you need to declare it. Most formatting is done before the text, like headings and lists, but this newline without a new paragraph is declared with two trailing spaces.

    • schipelblorp@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      2
      arrow-down
      2
      ·
      6 days ago

      I
      declare
      it
      by
      hitting
      an
      entire
      button
      dedicated
      to
      making
      a
      new
      line
      that
      also
      makes
      a
      new
      line
      in
      the
      editor
      I’m
      looking
      at
      creating
      a
      new
      line
      after
      I
      hit
      the
      button
      that
      creates
      a
      new
      line.

      It doesn’t make sense from a user perspective, whatever the format is (provided your users aren’t programmers).

      • whaleross
        link
        fedilink
        arrow-up
        5
        arrow-down
        1
        ·
        6 days ago

        Well, you are free to declare your own flavour and try get it supported by whatever editors and libraries you use. Damn, you can make up your own format that works in any particular way you want to. I bet in this time and age you could vibe code it with functions to your heart’s desire.

        But bitching about it to people that are trying to be helpful and explain why it is like it is will not render much other result than said people dropping you into their blocklist for being annoying.

        • schipelblorp@sh.itjust.worksOP
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          6 days ago

          Fair. Apologies.

          This issue is that you gave me kind of a detailed answer that didn’t really answer my question: What is the BENEFIT of doing it this way in the face of unexpected behavior to a naive user? Two answers others have given are that it allows easier cut-and-paste, and it allows users to break up their text for their own readability on narrower displays while still allowing it to be formatted to fit the final screen. Your answer of “Is is the way it is because that’s the way it is” is logically unassailable, yet lacks explanatory power.