3 ms·
Doesn’t seem awful - ++[, —[, and %%[ are all pretty unlikely to collide with the content of your average document. It is a bit messy once suggestions get nest
by mock-possum 3y ago
Doesn’t seem awful - ++[, —[, and %%[ are all pretty unlikely to collide with the content of your average document.
It is a bit messy once suggestions get nested, and given the option I’d still strongly prefer visually separating the change suggestions from the original content by pulling them out to aside blocks, but - if you held a gun to my head and forced me to do it all in plaintext, I wouldn’t hate this method.
- dash2 3y agoI'll think about that. Some syntax like %%[ % ... would work % for an aside... %%] but I wonder if it is too much effort for most people to arrange. The html formatter prints comments in <aside> blocks, which is possibly incorrect but the closest semantic match.
- jayd16 3y agoI don't know that nesting is a problem. It's somewhat nonsensical from a single edit perspective and if we're allowing multiple edits merged together then all bets are off on making sense of this or working with it. If two deletions partially overlap then they can't be acted on easily either.
- jimbobthrowawy 3y agoUntil they start using this system for suggesting changes to the documentation for this system itself. I am unsure if the suggestion files are meant to just be snippets long enough to uniquely identify where changes are meant to go, or the whole file again but with change suggestions.