At the moment I’m trying to keep .bikemd and .md separate, because .bikemd is a pretty specific subset that also breaks some things. I don’t want people to open any old .md document in Bike, save, and then have much of their structure altered/lost.
I think in next iteration of the format this will be changing, though I’m not sure by how much. I think in next iteration Bike will be generating fully valid recursive list markdown. But it still won’t be able to read all markdown structure.
I guess I could detect those read cased and add an alert before saving… anyway, let me explore what the final format will look like first, then can decide how to categorize it.
Yes, I think that’s a good solution if nothing else is found.
At the very start of a file, right after the first row (except when it’s a blockquote),
If the second row is a list (ul or ol),
After closing and reopening the file, Bike automatically inserts a blank line between the 1st and 2nd row – regardless of the indentation level of the second row.
This doesn’t happen elsewhere in the document – only at the beginning.
Additionally highlighted text appear ib Bike as <mark>Highlighted text</mark>after saving and reopening the .bikemd file