Markdown tests
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Mar 2024
77 points (100.0% liked)
Sync for Lemmy
15132 readers
15 users here now
๐
Welcome to Sync for Lemmy!
Welcome to the official Sync for Lemmy community.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Community Rules
1- No advertising or spam.
All types of advertising and spam are restricted in this community.
Community Credits
Artwork and community banner by: @MargotRobbie@lemmy.world
founded 1 year ago
MODERATORS
The bullet points in my comment here render correctly in the official Lemmy frontend, but not in Sync: https://lemmy.world/comment/6271596
I think a way to make them work is to add two spaces after each line. Here's a test...
Hopefully that works.
It did :-)
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...
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 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.
Ah, I see - thanks for the detailed explanation. I think I sort of knew that, but got mixed up when replying on bullets.
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.
Yeah, sorry, I got mixed up, so my 'solution' wasn't really a fix at all.
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:
This should make a bulleted list in Sync:
Source:
Yes, that was the case. Sync screenshot:
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.
This is an example of a numbered list item that is long enough to likely wrap onto a second line on most phones.
This is another numbered list item that is intended to do the same thing in order to see how readable they are together.
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.
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.