@AndrasDeak I didn't confirm that the rendered markdown works until I opened the same markdown file in a markdown previewer application called MacDown. So the issue is with Visual Studio Codes renderer.
Maybe I'll open an issue, maybe not.
@Andras Do you know whether MacOS can use the same file system that is used on Linux? A file system such as extension 4?
@AndrasDeak cat should be fine. I tended to use dd, but several people here on U&L pointed out that it has no advantages over cat. dd shows the amount of written data when sent a USR1 signal, it helps you organize your day when overwriting a huge & slow HDD. (I also thought dd could be optimized to be faster, but I was probably just struggling to make it as fast as cat :-)
@fra-san my concern was regarding the fact that /dev/zero doesn't have an inherent size. The cat suggestions I know, but only in the context of copying images and stuff.
It's not perfect, but I have mine setup so it displays this:
# Heading
This is a list:
* foo
* bar
And `inline code` above:
indented code
on multiple
lines.
And here's a quote:
> How would vim/emacs show rendered markdown? With included images and headings and shit?
I would like to use the SE flavor of markdown in my emacs. The default Markdown mode has some features (backticks and indentation mark code, # makes a header and > also changes the font) but I would also like to have:
* to make a list item, including indentation.
[foo](http://example.com) to sh...
Eh, it's been a while. I use this for my README files and it's quite useful. Not perfect, but enough to give me some basic formatting which is all I really need.
I've mounted a partition I just created manually with fdisk. Using sudo mount -o loop /dev/sdb tmpdir/ I get "WARNING: source write-protected, mounted read-only.". Is this normal? Googling for the error gives me mostly localization hits...
It's a "W95 FAT32" partition that's the only inhabitant of /dev/sdb with a "dos" partition table (MBR?).
and it's a USB stick so I couldn't have accidentally turned it read-only with a hardware switch
hmm, perhaps I used the wrong type of FAT
(nope)
OK, I caved and used debian's graphical disk utility, now it's working. Fdisk output looks the same... Oh well.