4 ms·
> I want the supreme flexibility of going from state A to B through some ill-formed textual editing Seems like the author agrees with you (albeit in a differen
by bradrn 4y ago
> I want the supreme flexibility of going from state A to B through some ill-formed textual editing
Seems like the author agrees with you (albeit in a different article):
> … the traditional structural editors do tend to impose some limitations … But these are not the inherent qualities of structural editing. This is just the way someone chose to implement it. So, when I say that Rune provides seamless structural editing, what I mean is that the other kind of choices are possible: the kind where you are editing as if the structure is only apparent, but not in your face, and so, it's just like there are no seams.
— https://project-mage.org/the-power-of-structure#orgeb59167 https://project-mage.org/the-power-of-structure#orgeb59167
- avgcorrection 4y agoYup. Apparently.[1] Seems that we agree that your typical structural editor is either too gimped or to inflexible to be useful. But I believe him when he writes that it is possible to make a unified language for editing all kinds of structures. I certainly wouldn’t wanna learn a new editing mode for every little yaml/json/java/rust/yaml-superset/yaml-superset-superset. [1] But I don’t have time right now to read that main article to find out, since Firefox claims that it is a 2 hour+ read. :p