scroll

This was SO helpful. Thank you so much! Immediately I realize that we need placeholder text in the textarea. Just tried to do it but actually requires a CodeMirror plugin, so will have to tackle tomorrow (https://github.com/breck7/scroll/issues/135). I was rooting for you to press a keyboard key that would trigger the autocomplete, such as "n", and then it may have clicked, but so helpful to see your (painful) experience so I know we need to surface that better, and provide more guidance. Tomorrow's version should be a lot better. Thanks again!!! Also, appreciated the commentary on the blog post. Definitely not my best writing, and I will clean that up at some point too. This made my day. Thank you.

I should make this easier to use any day now. High on my priority list. Here's the issue: https://github.com/breck7/scroll/issues/133

Super helpful! Thank you! Fix pushed: https://github.com/breck7/scroll/commit/dc10ea246c54f1ae1d4c...

Here is how you would do your image example in Scroll: rst: .. image:: example.jpg :alt: alttext scroll: image example.jpg caption alttext "Directives" in rST are "Parsers" in Scroll. The item above would be parsed by the `imageParser`, which at ~50 lines of code (https://github.com/breck7/scroll/blob/b8fd72aa38742cc6cd575f...), is actually more code than the average parser. To write your "exercise extension" in Scroll, you would just need to write a few lines of code definining an "exerciseParser". You could put that in the same file you use it in, or in a file named "exercise.parsers". I think you should explore Scroll -- https://scroll.pub/ -- might do everything you need in a simpler way!

Just don't make it easy for them by showing them https://github.com/breck7/scroll/tree/main/parsers

> Regardless if you specialize in React, Rails, Django, Next, Java, C#, or ObjectiveC, you probably use templates to start new projects. Java, C#, or ObjectiveC devs are unlikely to want their first command at the shell to start with `npm`, or the software supply chain fiasco npm drags in. That said, to jump in, here's a better starting point than this HN post link: - Overview: https://scroll.pub/ - Not helpful: https://notation.scroll.pub/ - More helpful: https://scroll.pub/tutorial.html - Source: https://github.com/breck7/scroll If you want more, you can sponsor breckyunits lab for $499,999 a year: https://breckyunits.com/lab.html

I enjoyed the article even though I'm in the opposite camp. > Context-free grammars, and their associated parsing techniques, don't align well with real-world compilers, and thus we should deemphasise CFGs (Context-Free Grammars) and their associated parsing algorithms. I agree with this. I think CFG are highly overrated. Top down recursive descent parsers are simple and allow you to craft more human languages. I think building top down parsers is something every dev should do. It's a simple technique with tremendous power. I think the source code for Scroll (https://github.com/breck7/scroll/tree/main/grammar) demonstrates how liberating moving away from CFGs can be. Easy to extend, compose, build new backends, debug, et cetera. Parser, compiler, and interpreter for each node all in one place. Swap nodes around between languages. Great ev

https://scroll.pub/ has made RSS irrelevant. https://github.com/breck7/scroll/commit/0ca22e118e1cc9a79eb9...

> Maybe youre looking for a way to graph those nodes and relations? This is one thing I was thinking about, eventually. For now I'm just thinking about sort of a collection of writing prompts to help me think more clearly. > its definitely something i'd contribute to Cool! The eventual destination would probably be this folder: https://github.com/publicdomaincompany/scroll/tree/main/gram... For example, right now there is a "question" node. Often when writing I find it a good prompt to just start writing a bunch of questions on the journey to fleshing out an issue.

I found out that the author of this article wrote it using a markup language called (confusingly) Scroll: https://scroll.pub/. I'm not sure I want to bother learning another markup language when there are many extensions to Markdown already, but this author apparently favors the multi-column layout. I find scrolling all the way to the bottom of a thin column to get old fast, however, especially when the article is longer than can fit into a single page. It's pretty easy to constrain the height of the article text div element to be slightly less than screen height (using `height: 100vh`, or maybe slightly smaller if you have a header), which makes the columns fit vertically within the screen but causes more columns to appear off-screen to the right. However, you can override PageUp and PageDown to scroll left and right instead: https://git

Reading a single article is pretty bad on desktop, right? Here's the source for that article in the interim: https://github.com/breck7/breckyunits.com/blob/main/insist-o... I haven't yet gotten the time to improve the desktop experience but there are a few issues tracking it: https://github.com/publicdomaincompany/scroll/issues Sorry about that! Hope we get it fixed soon.

This is great! The whole "Git is eating the database world" trend is picking up steam. MDN/Yari, mentioned recently on here was another similar one https://github.com/mdn/yari I am planning on doing something similar to Offbase with Dub (https://github.com/treenotation/dumbdown/tree/master/dub). Each post will be written in Dumbdown, but then also a whole "blog" (posts, settings, pages, etc), you will be able to view/edit in a single textarea, and copy/paste the whole thing. So you should be able to write a whole site in the client side JS app, use local storage for persistence, and then copy/paste either the raw Tree Notation files to import/export the site, or just the compiled HTML. Then just need a one click "write this site to a Git repo", and then GitHub/GitLab/etc can handle long term persistence, version control, and site hosting.