Strikethrough text on PieFed?
-
Strikethrough isn't mentioned on this page
https://piefed.social/community/fediverse/wiki/piefed-markdownBut I'll try a few things here anyway.
Fourth of July weekendLooks like the first thing I tried works! Double tildes before and after the text.
~~Fourth of July weekend~~Putting that in a code block still strikes through the text, though, instead of showing the tildes. (At least, it does in Preview.)
What about single line code?
~~Fourth of July weekend~~ -
What about single line code?
~~Fourth of July weekend~~Strikes through instead of showing the tildes.
-
Strikethrough isn't mentioned on this page
https://piefed.social/community/fediverse/wiki/piefed-markdownBut I'll try a few things here anyway.
Fourth of July weekendLooks like the first thing I tried works! Double tildes before and after the text.
~~Fourth of July weekend~~Putting that in a code block still strikes through the text, though, instead of showing the tildes. (At least, it does in Preview.)
Ugh, more diving into the
markdown_to_htmlfunction is in my future. Formatting like that shouldn't happen inside code regions. -
Ugh, more diving into the
markdown_to_htmlfunction is in my future. Formatting like that shouldn't happen inside code regions.Sorry, I didn't mean to make you 'ugh'
-
Sorry, I didn't mean to make you 'ugh'
No worries! It's actually been super helpful to have people like you testing and reporting all these weird cases. I think the root cause of a lot of these markdown -> html issues is that the underlying python library that piefed uses has a weird plugin system to enable different markdown features and they sometimes play weird with each other. One of those extras is the strikethrough syntax, and it seems as though it doesn't respect code regions (another extra). So, I just need to do some pre-processing of the text.
Basically, this is going to be a similar fix to the double-bold problem from a little ways back. I should have a fix in the next day or two.
-
No worries! It's actually been super helpful to have people like you testing and reporting all these weird cases. I think the root cause of a lot of these markdown -> html issues is that the underlying python library that piefed uses has a weird plugin system to enable different markdown features and they sometimes play weird with each other. One of those extras is the strikethrough syntax, and it seems as though it doesn't respect code regions (another extra). So, I just need to do some pre-processing of the text.
Basically, this is going to be a similar fix to the double-bold problem from a little ways back. I should have a fix in the next day or two.
IIRC, there's another
codevs formatting conflict: Spoiler inside code block.:::spoiler SPOILER! Some spoiler text ::: -
IIRC, there's another
codevs formatting conflict: Spoiler inside code block.:::spoiler SPOILER! Some spoiler text :::Yeah, I am going to try to put something together that basically prevents any markdown parsing inside code sections. The code portions should be unformatted in any way.
-
Ugh, more diving into the
markdown_to_htmlfunction is in my future. Formatting like that shouldn't happen inside code regions.~~this shouldn't have a strike through it~~~~neither should this~~::: spoiler This shouldn't be a spoiler. ::: -
~~this shouldn't have a strike through it~~~~neither should this~~::: spoiler This shouldn't be a spoiler. :::See above, this is fixed now.
-
See above, this is fixed now.
~~Fourth of July weekend~~
:::spoiler Spoiler Spoiler :::Thanks!
