Re:The Eno notation language
by teddyh on Thursday August 16, 2018 @05:56AM
(#17773294)
Here, “cities” looks like a comment, but it is part of the syntax, otherwise this example code would not work:
The actual comment syntax is “>”:
[ Parent
| on HN ]
Yes exactly - Hashes denote 'sections' in eno!
In the language design phase this was heavily inspired by markdown, because of the already widely familiar concept of 'headings' - I collected feedback from users that (although they showed considerable anxiety given the prospect that they were to use text files to edit their content in the future instead of a fancy web interface) they found working with markdown (quote) "super easy", so markdown was therefore an influential factor for some aspects of the language design. :)
Re:The Eno notation language
by jacobevelyn on Thursday August 16, 2018 @09:06AM
(#17774257)
This is a really cool project! I don't need quite the power of eno (yet!) in my CLI journaling app[1], but I similarly value the power of users being able to just easily read and write their own data. (I went with Markdown for the data store.)
Thanks for the encouragement!
I like the philosophy of friends! (even though I too don't need quite the power of it (yet). ;))
Re:The Eno notation language
by fnordsensei on Thursday August 16, 2018 @08:29AM
(#17774014)
It looks like the H1 tag in markdown, where the number of #'s indicate title level.