If you come across something that doesn’t work pop it here

  • tb_@lemmy.worldEnglish
    14·
    9 months ago

    Code blocks in quotes appear a little funky.

    Some line of code

    
> Extended quote
> ```
More code

    Further extended quote

  • Coelacanth@feddit.nuEnglish
    10·
    10 months ago

    Spoiler formatting was a big one, Lemmy wants to do it like this, I think:

    Some paragraph text.

    Spoiler Title

    Some spoiler elements

    Other paragraph text.

    EDIT: the main issue being Sync not displaying the spoiler title properly

    • can@sh.itjust.worksEnglish
      2·
      9 months ago

      Works when viewing this comment page but when looking at your profile page it’s blank. Is this expected?

  • Stovetop@lemmy.worldEnglish
    8·
    9 months ago

    !spoiler spoiler Test Comment

    with line breaks!<

    
with line breaks!<```

Saw this comment in the wild which does not appear correct in Sync.

https://discuss.tchncs.de/comment/8334366

In Sync it looks like this:

![](https://lemmy.world/pictrs/image/a660f68f-f78b-41a8-ae15-17a8cd896c3e.jpeg)

On Lemmy via browser, it looks like this:

![](https://lemmy.world/pictrs/image/ed917b91-cdf6-401a-92e0-01462790b8ce.jpeg)
  • Victor@lemmy.worldEnglish
    5·
    10 months ago

    Not sure if code blocks are supported at all (I’ll test using this comment); I know inline code strings are, but blocks I’m not sure.

    Either way, in the editor, I’m missing buttons for both inserting inline code and a code block.

    Speaking of messages, I can’t seem to find a way to mark a message/comment reply as unread. I would like that very much.

    #!/bin/fish
#Testing a block of code
if true
  printf "yes"
else
  printf "no"
end
    • CrayonRosary@lemmy.worldEnglish
      4·
      10 months ago

      I’ve noticed that Sync requires two newlines between the preceding sentence and the bulleted list, but the Lemmy website does not, nor does Eternity. That appears to be the problem with the list you posted.

      This might not make a bulleted list in Sync:

      • one
      • two
      • three

      This should make a bulleted list in Sync:

      • one
      • two
      • three

      Source:

      This might not make a bulleted list in Sync:
- one
- two
- three

This should make a bulleted list in Sync:

- one
- two
- three

      Yes, that was the case. Sync screenshot:

      1000022013

      • Stovetop@lemmy.worldEnglish
        2·
        9 months ago

        • This is an example of a bulleted list item that is long enough to likely wrap onto a second line on most phones.

        • This is another bulleted list item that is intended to do the same thing in order to see how readable they are together.

        • This is a third bulleted list item that has an additional line break between the previous list item.

        1. This is an example of a numbered list item that is long enough to likely wrap onto a second line on most phones.

        2. This is another numbered list item that is intended to do the same thing in order to see how readable they are together.

        3. This is a third numbered list item that has an additional line break between the previous list item.

        These don’t seem very readable to me, making dense walls of text. I feel like bullets and numbers should indent the paragraph to more easily see the separation between list items.

        • CrayonRosary@lemmy.worldEnglish
          3·
          9 months ago

          The additional line breaks aren’t doing anything, as I’m sure you can see.

          The indent should be an option, if anything. At large font sizes, or small screens, that forced indent might be wasting a lot of space. Especially for nested lists.

          Although, as it turns out, Sync barely indents nested lists. That alone makes it hard to read, too.

          I’d support the indent you mention. It would make nested lists much easier to read, too.

          • Level 1
            • Level 2. Perferendis est reprehenderit saepe atque architecto sunt est. Libero quia velit qui ut non maiores porro blanditiis. Cum rerum velit modi nisi est. Qui qui in qui. Ducimus omnis dolores doloribus cumque a sunt
              • Level 3. Perferendis est reprehenderit saepe atque architecto sunt est. Libero quia velit qui ut non maiores porro blanditiis. Cum rerum velit modi nisi est. Qui qui in qui. Ducimus omnis dolores doloribus cumque a sunt
                • Level 4. Perferendis est reprehenderit saepe atque architecto sunt est. Libero quia velit qui ut non maiores porro blanditiis. Cum rerum velit modi nisi est. Qui qui in qui. Ducimus omnis dolores doloribus cumque a sunt
            • Level 2. Perferendis est reprehenderit saepe atque architecto sunt est. Libero quia velit qui ut non maiores porro blanditiis. Cum rerum velit modi nisi est. Qui qui in qui. Ducimus omnis dolores doloribus cumque a sunt
    • SanguinePar@lemmy.worldEnglish
      52·
      10 months ago

      I think a way to make them work is to add two spaces after each line. Here’s a test…

      • Line one
      • Line two
      • Line three

      Hopefully that works.

      It did :-)

      • CrayonRosary@lemmy.worldEnglish
        6·
        9 months ago

        That’s a placebo and it’s not doing anything. Bulleted lists never need two spaces at the end of each line. You only use two spaces at the end of line that are not in bulleted or numbered lists.

        The bug is that Sync requires a blank line before you start the bulleted list. The Lemmy website doesn’t require that.

        Here is your comment with no spaces at the end of each line:

        spaces after each line. Here’s a test…

        • Line one
        • Line two
        • Line three

        See? It still works fine.

        Now here’s an example of what two spaces do.

        The first sentence below has a new line after each word but no spaces. The second sentence has two spaces and a new line after each word. The spaces force a line break to be rendered.

        This Is Not A List

        This
        Is
        Not
        A
        List

        Source of the above:

        This 
Is 
Not 
A 
List

This  
Is  
Not  
A  
List

        This feature of markdown was implemented to prevent text from emails and such from wrapping in funny ways when pasted into a comment (or whatever). Old emails often force line breaks after 80 columns of text and it looks goofy when viewed in a modern web browser if those line breaks are kept, so they are ignored. To preserve the line breaks, you add two spaces at the end of each line. That or you might prefer to write paragraphs with a hard wrap at some column, but other people shouldn’t have to suffer that.

        Adding the two spaces to lines in a bulleted list does nothing useful, but it also doesn’t break it, so of course it works.

        • SanguinePar@lemmy.worldEnglish
          3·
          10 months ago

          Ah, I see - thanks for the detailed explanation. I think I sort of knew that, but got mixed up when replying on bullets.

      • CMahaff@lemmy.worldEnglish
        4·
        10 months ago

        So I know that will make it look correct in sync, but I guess what I’m getting at is that the comment is an example that looks right in other clients but NOT in sync.

        Sync should show the list correctly like other clients do.

      • Zagorath@aussie.zoneEnglish
        8·
        10 months ago

        sharing it to someone without sync

        The bang syntax will work much better for anyone on Lemmy itself, regardless of which instance they’re on or which client they use, while the URL syntax is better when users want to share a link to a community off-platform.

      • SanguinePar@lemmy.worldEnglish
        4·
        10 months ago

        Ah, fair point. Maybe a concatenated version with both formats? Dunno. Not a huge issue to be fair :-)

  • can@sh.itjust.worksEnglish
    4·
    7 months ago

    Any progress being made here? I was really hoping that not being able to view certain communities such as !newbrunswick@lemmy.ca would be considering bad enough of a bug to bring a little development back.

  • can@sh.itjust.worksEnglish
    3·
    7 months ago

    I’m not sure if you’re still monitoring this or if I should make new thread.

    I just encountered a comment where they included a link with brackets in the url and it didn’t parse for me in Sync. I assumed it needed escape characters , which did make it a working link for me in app, but I got curious and checked the website and the original link worked fine there. Maybe the Lemmy web ui will escape characters in links by default?

  • pivot_root@lemmy.worldEnglish
    3·
    9 months ago

    While this isn’t strictly a markdown issue, it is slightly related. Link domain indicators are handled specially for Reddit, and they probably shouldn’t be.

    This is a link to a Lemmy post. Sync appends (lemmy.world) after it.

    This is a link to a Reddit post. Sync appends (/comments/) after it.

    This is a link to an old.reddit post. Sync appends (/comments/) after it.

    This is a link to a Lemmy profile. Sync appends (lemmy.world) after it.

    This is a link to a Reddit profile. Sync appends (u/ljdawson) after it.

    I acknowledge that there would be technical difficulties in trying to make Sync identify ActivityPub users and posts, and the current implementation of showing the domain name is good, in my opinion.

    Reddit links should probably display the Reddit domain name, however. These links are external to Sync and would open a new browser page, and it’s more informative for the user to know the domain of the link they are opening.

  • DoomBot5@lemmy.worldEnglish
    41·
    10 months ago

    No text image links in post bodies. Usually see them in the format [](link here) don’t show up at all.

  • Stovetop@lemmy.worldEnglish
    3·
    9 months ago

    This is a spoiler message that I unhid before editing.

    >!This is a spoiler message that I unhid before editing.!<

    !This is a spoiler message that I left hidden before editing!<

    >!This is a spoiler message that I left hidden before editing!<

    This is the edit.

    • Stovetop@lemmy.worldEnglish
      3·
      9 months ago

      Not sure I’d count this as a markdown bug per se, but it seems that when you un-hide a spoiler and then edit your post, it treats the post as if the spoiler had never been there in the first place.