From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/33226 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Fritz Fritzy Newsgroups: gmane.text.pandoc Subject: Markdown: simple syntax for arbitrary nesting Date: Tue, 24 Oct 2023 23:06:49 -0700 (PDT) Message-ID: <5573f042-48a4-4115-8b1d-a86c13eb319an@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_388_1952554041.1698214009449" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22495"; mail-complaints-to="usenet@ciao.gmane.io" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBDOITKNXR4IRB6XA4KUQMGQEYVWUMXI-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Wed Oct 25 08:06:55 2023 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane-mx.org Original-Received: from mail-oo1-f55.google.com ([209.85.161.55]) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1qvX2c-0005go-Ug for gtp-pandoc-discuss@m.gmane-mx.org; Wed, 25 Oct 2023 08:06:54 +0200 Original-Received: by mail-oo1-f55.google.com with SMTP id 006d021491bc7-583fb42332csf7282071eaf.2 for ; Tue, 24 Oct 2023 23:06:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1698214013; x=1698818813; darn=m.gmane-mx.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:x-original-sender :mime-version:subject:message-id:to:from:date:sender:from:to:cc :subject:date:message-id:reply-to; bh=BTiZIOXymDn/ogEEcpMkgRmPRstgaK7/MKVwkakQPvg=; b=BL81/RJDVp6BBX9IHYUJRl3JrcUU3F3719saIHrlYwMX7XxnOkJrh6+lxemr2VsQBy vdWRgl95BMBQGfx8T+eZA4BLRTZedrsiO1I08b0JV6M4iX5alMqljcylxz/lBXIYRKaU wLmgdumMnIwtike0fBdPlUcD1Y/S0q92ysEz+L1X1pMpMKFH5I7VtaHFdqDIXPyngSh9 NyzEE19LQfZPHAY34ajvMpP/yq9+NXkw+rbWgjjlud17R2g9MJ4o3r43kfqpYPGVxAmy doeLq81An2D+mEeZL1OkO6z8xklsRu8hSEGsbpRx3oP+j2bzdaJgrdjPNXVRrhViwPiD lPHw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698214013; x=1698818813; darn=m.gmane-mx.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:x-original-sender :mime-version:subject:message-id:to:from:date:from:to:cc:subject :date:message-id:reply-to; bh=BTiZIOXymDn/ogEEcpMkgRmPRstgaK7/MKVwkakQPvg=; b=G7RLccJ8IP3aP4PHmiVo4Xs/U8BdfjfkZWD9RN9bey9Vi49t79h2ZOdmJEo8YtXBei rD5sIUW/A2P22m/9saYB81lBcf9NrgrNUFaqqjAcqpjsEm6wjoA7LzT7B2PTNa8zTVNo 0pTS/Z0uGSXGh6E7vpMkkQWDdQS75W3y3xJNQn8XRJS/nir3kQBYcrhzkOmdLVHTyb1v pjkd7mubZ0D101doSk0SdrigZ18yK7BwKg6qz6tFKtZn8BEIRFVUi4Yu7M7KSHNz3hA/ WGENbjhZI1lyimT+B4vilshVJeVGRivnLIjv0CyJw3ygX/+dnpdeaXv7OBFdjhdWox/b BPXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698214013; x=1698818813; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :x-spam-checked-in-group:list-id:mailing-list:precedence:reply-to :x-original-sender:mime-version:subject:message-id:to:from:date :x-beenthere:x-gm-message-state:sender:from:to:cc:subject:date :message-id:reply-to; bh=BTiZIOXymDn/ogEEcpMkgRmPRstgaK7/MKVwkakQPvg=; b=gGbSKvcV7gUkCKj45AfO0tvGheri8TjUA2K0waf0I8YgkrmtddpiZJEkZn/nDyQ6vK ZjvkD1MUYmVGxAGHv0LMjvxXQXrIZ9mj9/4EnE3z5mQhwjQSEXXcnCOt7BRn9S5yQ1Vf QbDOpgmhf5364x/VMt3c6ISToA5/bqHbd+VfekhatpO1nF9MzFYxDJgeDN+071zNS7+2 Ozq3UZl48hnp3yF0A8w5prdG4eM6iMpbFWJeL7Lj+3tVqKogIrJHGv0w0dqmWBgk45kF N1dSCIkPrtZW9fYQMjnL1Duau9qxzoicc3nQhDzOJELbBdnlNRCSG1dK7I6Sqhnz8Ccw Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: AOJu0Yws9sT/PxrfzEUjK1WnLlZopgY5Ugs1r8CvdF07szsZ11VoMAGo 4lPqDA5Hkz+B6QdIc6mz4XM= X-Google-Smtp-Source: AGHT+IHDMEAS6w0/qvZGmFCDVXvEDsyG1fkwiADNKIgYMSXku6+yIxxQwa2QHgtDlQcVFl4V87D+fw== X-Received: by 2002:a4a:e042:0:b0:571:aceb:26c8 with SMTP id v2-20020a4ae042000000b00571aceb26c8mr14599048oos.3.1698214013807; Tue, 24 Oct 2023 23:06:53 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a4a:33d3:0:b0:581:e7bb:9ad5 with SMTP id q202-20020a4a33d3000000b00581e7bb9ad5ls2834793ooq.1.-pod-prod-07-us; Tue, 24 Oct 2023 23:06:50 -0700 (PDT) X-Received: by 2002:a9d:7483:0:b0:6c4:76b9:fe44 with SMTP id t3-20020a9d7483000000b006c476b9fe44mr4034209otk.7.1698214010039; Tue, 24 Oct 2023 23:06:50 -0700 (PDT) X-Original-Sender: Emile.Valjean-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.io gmane.text.pandoc:33226 Archived-At: ------=_Part_388_1952554041.1698214009449 Content-Type: multipart/alternative; boundary="----=_Part_389_333659133.1698214009449" ------=_Part_389_333659133.1698214009449 Content-Type: text/plain; charset="UTF-8" Hi, Using markdown, I've often been frustrated by 1. Its flat/non-recursive/non-nested nature, by which I mean that you mostly cannot write "arbitrary" markdown inside most elements, and if you can, you have to be very careful with whitespaces/indentation/etc. 2. The impossibility to easily interlink to arbitrary parts of the document. To solve both issues, I'd like to propose an extension that allows "simply" using braces (or some other punctuation pair) to allow nesting, with an option to tag/add attributes to the contents like that. In some more details: - The format would just be `{ content }` or `{ content }{#id .class}` to be able to add attributes to a block. - If the content between braces contains new lines, the first new line sets the indentation level for the rest. There could be a point to be made to put the attributes before the content, but I'm not sure what kind of form that would take. Maybe something like `#id{content}{.class}` could be used: only the identifier can come before the content, and has to be a valid identifier (alphanum, underscore, dash)? I think this syntax would not clash with that much of what's already existing: mostly just the already existing attribute syntax. A potential solution to that would be to use a different character pair for nested blocks, but `[]` is already used a lot. I've looked at implementing that as a custom filter, but I think it has to be an extension baked in pandoc itself. Cheers -- You received this message because you are subscribed to the Google Groups "pandoc-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/5573f042-48a4-4115-8b1d-a86c13eb319an%40googlegroups.com. ------=_Part_389_333659133.1698214009449 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

Using markdown, I've often been frustra= ted by

  1. Its flat/non-recursive/non-nested nature, by= which I mean that you mostly cannot write "arbitrary" markdown inside most= elements, and if you can, you have to be very careful with whitespaces/ind= entation/etc.
  2. The impossibility to easily interlink to arbitrary pa= rts of the document.
To solve both issues, I'd like to propos= e an extension that allows "simply" using braces (or some other punctuation= pair) to allow nesting, with an option to tag/add attributes to the conten= ts like that.
In some more details:
  • The format would= just be `{ content }` or `{ content }{#id .class}` to be able to add attri= butes to a block.
  • If the content between braces contains new= lines, the first new line sets the indentation level for the rest.
    • There could be a point to be made to put the attributes before the c= ontent, but I'm not sure what kind of form that would take. Maybe something= like `#id{content}{.class}` could be used: only the identifier can come be= fore the content, and has to be a valid identifier (alphanum, underscore, d= ash)?

    I think this syntax would not clash with t= hat much of what's already existing: mostly just the already existing attri= bute syntax. A potential solution to that would be to use a different chara= cter pair for nested blocks, but `[]` is already used a lot.

    I've looked at implementing that as a custom filter, but I thi= nk it has to be an extension baked in pandoc itself.

    =
    Cheers


--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d= /msgid/pandoc-discuss/5573f042-48a4-4115-8b1d-a86c13eb319an%40googlegroups.= com.
------=_Part_389_333659133.1698214009449-- ------=_Part_388_1952554041.1698214009449--