Aftertext

Dev tools

markup language

SHOW HN2021

Aftertext

It starts getting clunky but I added some new keywords to handle the multiple hits scenarios: match and…

breckyunits.com

#markup language#markdown alternative#text formatting#plain text markup

96points
36comments
#550of 2,533 in 2021
Top 22%of 2021 by points

How HN took it

MixedNo clear lean

6 positive, 11 neutral or asking, 2 mixed, 9 critical, out of 28 comments about the project. Thread score -0.13.

Design: 1 for, 8 againstIdea: 4 for, 0 againstExecution: 1 for, 1 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Readable word-based instructions instead of symbols

    From 2 comments
    • I like this a lot, and I think it's an important contribution! I think it's a major advantage that the formatting description is provided using words rather than combinations of…
      epicureanideal on HN
    • This is really cool. A bit verbose for my taste, but OTOH it could be easier to remember than markdown or html. For example, I often forget the syntax for links in markdown - do…
      hiyer on HN
  • Works well with collaborative plain-text editing (CRDTs)

    From 1 comment
    • Here's an interesting benefit this has over inline markup languages: it's natively compatible with text-based CRDTs. Normally, collaborative rich text editing is a strictly…
      doomrobo on HN
  • Useful for parallel text and translation annotation

    From 1 comment
    • This will be lovely for parallel text: annotating each word with its translation AND retaining the original as well as the annotations in readable form. Even overlapping ranges…
      dejj on HN

Objections

  • Verbose, repeats the text for each markup instruction

    From 3 comments
    • Seems verbose having to repeat everything so often. Given how often I alias stuff after only a few repeats, I can see this becoming annoying quick. Still always cool to see…
      torbTurret on HN
    • The thing I like about markdown and similar syntax's are the simplicity and succinctness. When you take the markup out of context, well you lose context. My issue with this would…
      account-5 on HN
    • This is really cool. A bit verbose for my taste, but OTOH it could be easier to remember than markdown or html. For example, I often forget the syntax for links in markdown - do…
      hiyer on HN
  • Selectors depend on the text, so edits must be made in two places

    From 2 comments
    • This is an interesting idea, though I'd be worried that it could complicate the editing process compared to mixed content and markup. In particular, the examples of selectors in…
      Minor49er on HN
    • This is horrific, imagine changing your text and having to update the indices
      doovd on HN
  • Byte/index-based selectors are fragile when text changes

    From 2 comments
    • That looks very inflexible for later edits, marking characters or words means a potentially cumbersome recounting if something is reworded or just if a typo is fixed. Also, I get…
      dspillett on HN
    • This is horrific, imagine changing your text and having to update the indices
      doovd on HN
  • Cannot easily target repeated words; only first match used

    From 3 comments
    • Neat idea, though as I was playing around with it I noticed right away that the following seems to be impossible (or else very non-obvious) via Aftertext: "How much wood could a…
      yellowapple on HN
    • Interesting lang. ``` aftertext It's the difference between helping your Uncle Jack off a horse and helping your uncle jack off a horse. italics off italics off ``` Yields (in…
      renewiltord on HN
    • The current implementation just matches the first match, as that was the simplest and most common occurrence. But I have indeed hit this footgun (though it in my case involving…
      breck on HN

Requests

  • Regex or matchAll selectors

    From 4 comments
    • > but with Aftertext the bytes increase linearly with N, the size of the span you are marking up Maybe allow regexes for the span?
      Turing_Machine on HN
    • Or dive into AWK-style selectors all the way: ``` aftertext The fox jumped the dog /^The/ italics 15,18 italics ```
      dejj on HN
    • > regexes You could do that. I have not needed regex selectors yet but would be easy enough to add if someone had a need.
      breck on HN
    • It starts getting clunky but I added some new keywords to handle the multiple hits scenarios: match and matchAll. Demo:…
      breck on HN
  • Markdown conversion

    From 1 comment
    • I like this a lot, and I think it's an important contribution! I think it's a major advantage that the formatting description is provided using words rather than combinations of…
      epicureanideal on HN
  • Inline syntax option

    From 1 comment
    • I like this a lot, and I think it's an important contribution! I think it's a major advantage that the formatting description is provided using words rather than combinations of…
      epicureanideal on HN

Questions

  • How to distinguish emphasis markers from literal text

    From 1 comment
    • How do you distinguish between *text that looks like this* and _text that looks like this_?
      citizenkeen on HN
  • Whether it has improved productivity for the maker

    From 1 comment
    • Very cool, I'm curious have you noticed any productivity improvements after using this to write?
      jawerty on HN

Alternatives named

  • ROFF/groff

    From 2 comments
    • It's actually extremely old school. ROFF is similar to this You can just make it .p, .i, .b, etc. .br for line break. https://www.systutorials.com/docs/linux/man/7-groff_man/
      kristopolous on HN
    • Wouldn’t ROFF require putting the format commands in-line? Like so: ``` How much .i wood would a .i wood chuck chuck if a .i wood chuck could chuck .i wood? ``` I have no…
      dejj on HN
  • Markdown

    From 2 comments
    • This is really cool. A bit verbose for my taste, but OTOH it could be easier to remember than markdown or html. For example, I often forget the syntax for links in markdown - do…
      hiyer on HN
    • ``` aftertext Just a guess, but maybe bold a guess paragraph open aftertext a guess that could work. underline a guess ``` Might render to: ``` Just *a guess*, but maybe _a…
      merlincorey on HN
  • reStructuredText

    From 1 comment
    • Interesting. Seems like there is some overlap with reStructuredText.
      nerdponx on HN
  • Pollen

    From 1 comment
    • > Could Aftertext be made inline with a small number of symbols and result in a net reduction of symbols and greater explicitness and intuitiveness? For example, could an unusual…
      chipotle_coyote on HN
  • HTML

    From 1 comment
    • This is really cool. A bit verbose for my taste, but OTOH it could be easier to remember than markdown or html. For example, I often forget the syntax for links in markdown - do…
      hiyer on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/29643313)