I like plain text. I tolerate markdown. Markdown was designed as a shorthand for html. It gets stretched to do other stuff.

I created Brashtag [1]. It is simpler than markdown.

[1] https://github.com/PratikDeoghare/brashtag

▲

CrimsonCape an hour ago | parent | next [-]

Can you think a little more about your decision to strongly type code blocks. Some domains have no need for code escaping but do need blob text escaping (which you already have defined elsewhere.) Technically you could treat code via 'this is a bag named code with a blob, therefore it is code."

	▲	pratikdeoghare an hour ago \| parent [-]
		I wanted to keep the famaliar things. We write code blocks with backticks in markdown and slack and everywhere so I used those. In fact I used $ signs earliar then switched to backticks. > 'this is a bag named code with a blob, therefore it is code." This would make #code{} a special bag. Right now no bag is special. Also it would be hard to find the closing } if somebody wrote unbalanced paren code in the bag like #code{ func main() { }.

▲

gandreani 2 hours ago | parent | prev | next [-]

Why did you create it? What were you looking to solve address?

	▲	pratikdeoghare an hour ago \| parent [-]
		I had multiple frustrating experiences. I kept thinking I could just write things in some format in text and have some programs process it to do different things. So I created it. See how easy it is to write programs to process brashtag [1]. I can chat with llm, interact with jupyter kernel and do literate programming from any text editor all in the same document [3]. It took me like 10 minutes to build this mermaid like thing [2]. List of frustrations: - One day Anki crashed. --- You can just write #card{....} in a text file. Some program would read it and show flashcards in browser. - Another day JabRef crashed. --- You can just write #bib{....} put link to a paper and its citation info there and have a program download the paper and copy the citation to bib file. - Markdown parser processed mathjax wrong. Why keep trying different markdown parsers? Just write #h1{}, #b{} #i{} and just convert them to html tags. - Literate programming tool I was using failed at some corner case. - My notes were scattered across files and tools. I couldn't find anything. I tried to have a text file where sections were separated by four dashes. But that didn't allow nesting. Also, the parser I wrote for that hit corner cases. Why not just put #note{} #JIRA-334{} etc. in text file. [1] https://github.com/PratikDeoghare/brashtag#some-programs [2] https://github.com/PratikDeoghare/brashtag/tree/master/cmd/m... [3] https://www.youtube.com/watch?v=IMXgIE0Vljg

▲

someonebaggy 2 hours ago | parent | prev [-]

[flagged]

	▲	pratikdeoghare an hour ago \| parent [-]
		What if you wanted say footnotes? html does not have it. Imagine you could just say #footnote{This will become footnote} and have a little program that would produce html that will show it at the bottom of the page.