4 ms·
Interesting idea, I like the premise that people might build fancy ways to interact with this such as VSCode addons with a 'real' UI, but there will always be a
by cehrlich 5y ago
Interesting idea, I like the premise that people might build fancy ways to interact with this such as VSCode addons with a 'real' UI, but there will always be a plaintext fallback.
I already manage my hobby software projects using plaintext files, using a made-up syntax that is not quite org-mode, not quite xit, but that I'm also not too strongly attached to.
The one thing that jumps out of me that would make it hard to switch to xit that the spec currently doesn't allow lines to start with whitespace, which I use for grouping things. I settled on 2 spaces, but could also see 4 maybe being a better choice because of how it makes things line up.
(presented here with additional spacing because hn doesn't parse single newlines)
UI
[ ] Buttons
[ ] Front page call to action
[ ] Make it red
[ ] Make it really big
[ ] General
[ ] Increase padding
[ ] Stronger drop shadow
- jotaen 5y agoI didn’t include nesting in the first edition of the draft, because there might be some implications with it and I was curious for feedback on this. https://github.com/jotaen/xit/discussions/2 https://github.com/jotaen/xit/discussions/2 But it seems like my potential concerns are not shared that much, so I think the nesting should be added to the [x]it! spec.