|
|
|
|
|
by lapinot
1187 days ago
|
|
I'd encourage you reading through the thesis explaining the decisions and the thing in details. Just did skimmed through myself and all your concerns are easily answered (https://www.user.tu-berlin.de/laurmaedje/programmable-markup...). Your first concern is just wrong, afaik content and code live in different syntactic worlds. Code in content has a "#" sigil (and ends at some point) and content in code is delimited with square brackets. Your second concern is weird. For one off things you definitely just wrap it in a function call `#myweirdthing[blabla]`. Last remark: you're bikeshedding. Seeing your previous remarks i'm not sure you should. Makes complete sense to have a simple powerful syntax and a handful of shortcuts for markdown-level common typography. I'm absolutely not affiliated btw, just thought about very similar stuff for some time and been waiting for the release. I would've done a couple things sightly differently but the big decisions look very sensible and i'm sure they thought about it for a long time. Good work releasing this and thanks for the free software work! |
|