[HN Gopher] Suggestions: A simple human-readable format for sugg...
       ___________________________________________________________________
        
       Suggestions: A simple human-readable format for suggesting changes
       to text files
        
       Author : dash2
       Score  : 24 points
       Date   : 2023-12-27 11:22 UTC (11 hours ago)
        
 (HTM) web link (suggestions.ink)
 (TXT) w3m dump (suggestions.ink)
        
       | mock-possum wrote:
       | 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 wrote:
         | I'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.
        
       | bsmith89 wrote:
       | I've been looking for something like this!
       | 
       | I'm wondering how it compares to
       | https://github.com/CriticMarkup/CriticMarkup-toolkit
       | 
       | I haven't tried using either yet; does anyone here have any
       | opinions about features/ergonomics/tooling?
        
         | dash2 wrote:
         | CriticMarkup seems to emit more correct HTML, but is more
         | demanding (e.g. it recommends against embedded newlines). It
         | doesn't emit TeX. It does have more (i.e. any) editor syntax
         | files.
         | 
         | I mildly prefer having the marks outside the brackets:
         | ++[foo]++ seems easier to read than {++foo++} because the
         | "wrapping" is outside the "box".
        
       | drwu wrote:
       | I guess the way to suggest merging two paragraphs:
       | 
       | --[
       | 
       | ]--++[ ]++
        
       ___________________________________________________________________
       (page generated 2023-12-27 23:01 UTC)