I hope Bike 2.0 will support subscript and superscript. It is impossible to write without in an academic setting.
Happy to say, yes this is implemented.
3 Likes
Hi, thanks for your software. That is really what I was looking for. But without a minimum of markdown support, it is really useless to use for projects with other people 
For example, I would need to get some support of headers, so they get display as a node without the next line to get intended. Also, why is something like bold not support? Why should I buy a licenses for formatting, if formatting is not supported for md?
So the md file would look like this:
# This is a header
This is some **content**.
More content.
And in bike it would look like this:
This is a header
____ This is some content.
____ _____ More content.
I get that you don’t use markdown, and I think it could be better. But it’s one of the few file formats that everyone knows and will likely continue to use in the future.
If you need to collaborate on an outline Bike is unlikely to be your best choice. Someday down the road I hope to fix this (sync outline between people), but it’s still quite far down the road.
I “think” here you are talking more about copying/exporting content out of Bike and sharing it with other people?
Anyway, currently Bike has no built in markdown import/export support. There are some scripts that others have shared that do offer some markdown support, but nothings built in.
Bike does have built in support for rich text and html. And they both encode/decode bold text appropriately I think. Generally it should work to select part of your outline, Copy, and then paste (into email for example) and you should get rich text formatting persevered.
Let me know if you meant something different.
It has been on my list to also add built in support for Markdown import/export, but it’s not a strong priority at the moment. A particular challenge is there are multiple ways you might want to export your outline as markdown, so there’s not really a clear correct way to support it.
Bike 2 is in progress and that’s where my focus is.
A bit part of Bike 2 is to support extensions to Bike that add commands and other features directly… as opposed to the current Bike 1 system that allows automation of Bike, but through external scripts or shortcuts.
I believe this new extension system should make it easier to experiment with new features like this (markdown export/etc) the extensions are written in mostly normal typescript/javascript and you’ll be able to reuse lots of existing code to say generate the markdown that you want to see.
Hope that orients you to what’s possible now, what might be possible in future.
1 Like