public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Some code formatting for code block attributes in pandoc's markdown....
Date: Mon, 18 Jul 2022 17:29:37 +0200	[thread overview]
Message-ID: <CAMwawgPvUNc1Ttf1Z-T5QBx01OnXL0MQ8_3LnAYYmeehVyJgSg@mail.gmail.com> (raw)
In-Reply-To: <4d799efa-fe25-c4cb-c542-e18278f8415c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2508 bytes --]

Hmmm... I guess you can, but it doesn't get syntax highlighted properly by
Vim... strange...

On Mon, 18 Jul 2022 at 17:24, Sukil Etxenike arizaleta <sukiletxe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:

> Hi,
>
> Yes, you can. I've tried with Pandoc 2.18 and it worked fine, except in
> one case where I don't know what I did.
>
> Hth,
>
> Sukil
>
>
> El 18/07/2022 a las 17:15, A A escribió:
>
> Dear All,
>
> I'm designing my own writer and have ended up with something like this for
> how I would like to define some of my Code Blocks:
>
> ```
> ``` { #lst:imported-code-block .python firstline=4 lastline=8
> filename=imported-code-block.py }
> ```
> ```
>
> Is it possible to break down the identifier, classes and attributes of the
> code block in multiple lines in the source? It's beginning to look a bit
> cluttered and messy.
>
> Regards,
>
> Amine
> --
> 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/CAMwawgPfpCPP8ZHJox-QztJC2J73L_h5zT0due%3D-b-6npw7hHg%40mail.gmail.com
> <https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgPfpCPP8ZHJox-QztJC2J73L_h5zT0due%3D-b-6npw7hHg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> --
> 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/4d799efa-fe25-c4cb-c542-e18278f8415c%40gmail.com
> <https://groups.google.com/d/msgid/pandoc-discuss/4d799efa-fe25-c4cb-c542-e18278f8415c%40gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAMwawgPvUNc1Ttf1Z-T5QBx01OnXL0MQ8_3LnAYYmeehVyJgSg%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 3912 bytes --]

  parent reply	other threads:[~2022-07-18 15:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 15:15 A A
     [not found] ` <CAMwawgPfpCPP8ZHJox-QztJC2J73L_h5zT0due=-b-6npw7hHg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-18 15:24   ` Sukil Etxenike arizaleta
     [not found]     ` <4d799efa-fe25-c4cb-c542-e18278f8415c-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-07-18 15:29       ` A A [this message]
2022-07-18 16:16       ` John MacFarlane
     [not found]         ` <C46B3BA1-AA71-49DE-A15B-299173A4F045-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-07-18 18:02           ` A A
     [not found]             ` <CAMwawgMRm0o1YS6i+dchx1YHy4q03wQbEuzRGbfiuO6qaep9dw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-07-18 18:06               ` John MacFarlane
     [not found]                 ` <47D489F7-4FC9-444A-901B-A42FE3AB3A6A-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-07-18 18:09                   ` A A

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=CAMwawgPvUNc1Ttf1Z-T5QBx01OnXL0MQ8_3LnAYYmeehVyJgSg@mail.gmail.com \
    --to=amine.aboufirass-re5jqeeqqe8avxtiumwx3w@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).