public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Gwern Branwen <gwern-v26ZT+9V8bxeoWH0uzbU5w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Singleton block construct with attributes?
Date: Wed, 25 Aug 2021 11:20:02 -0400	[thread overview]
Message-ID: <CAMwO0gy-xX+GsbvCrPBjV1-BH2K2LP7w3+PZxttaS9pUFPLtNg@mail.gmail.com> (raw)
In-Reply-To: <CAEe_xxj-V3A-p31hUvuxy9WhJF_51-Lot_0R3zpnQGzHa-KuCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

If you simply want some sort of keyword to plop in, why the obsession
with attributes? There are lots of things you could write. The thing
I'd immediately think of is writing a little div or span with a class,
like:

     $ echo '[]{.pause}' | pandoc --from=markdown+native_spans --write native
    [Para [Span ("",["pause"],[]) []]]

Now you just match on `foo (Span (_, ["pause"], _) _) = rewriteCode
...` in your API use.

-- 
gwern
https://www.gwern.net


  parent reply	other threads:[~2021-08-25 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25  8:23 Axel Rauschmayer
     [not found] ` <066d8f5e-ede0-4705-9f38-4add41cb7ff1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-25  9:41   ` William Lupton
     [not found]     ` <CAEe_xxj-V3A-p31hUvuxy9WhJF_51-Lot_0R3zpnQGzHa-KuCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-08-25 15:20       ` Gwern Branwen [this message]
2021-08-25 16:14       ` John MacFarlane
2021-08-25 16:33   ` BPJ
     [not found]     ` <CADAJKhCHPhqJz_8b8EikbNoh_Ytyn5iPefS3cvkQA=tjD94nMw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-08-25 16:37       ` BPJ
2021-08-25 19:08   ` Axel Rauschmayer
     [not found]     ` <60bb4763-544c-4a15-b09c-d545aa60dcb1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-25 19:55       ` Axel Rauschmayer
     [not found]         ` <b77d6ced-e951-4fec-8bb3-5ad8ed1c76a4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-08-25 20:29           ` John MacFarlane

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMwO0gy-xX+GsbvCrPBjV1-BH2K2LP7w3+PZxttaS9pUFPLtNg@mail.gmail.com \
    --to=gwern-v26zt+9v8bxeowh0uzbu5w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).