ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan via ntg-context <ntg-context@ntg.nl>
To: Mojca Miklavec via ntg-context <ntg-context@ntg.nl>
Cc: Aditya Mahajan <adityam@umich.edu>,
	Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: How to do code listings & sections from XML (AsciiDoc)
Date: Fri, 12 Aug 2022 17:20:18 -0400 (EDT)	[thread overview]
Message-ID: <nycvar.YAK.7.78.908.2208121718560.280663@nqv-guvaxcnq> (raw)
In-Reply-To: <CALBOmsYOovebuf=ptKg9i0OBfp2XyOOFX_JstWDRaDxf1Fo7BQ@mail.gmail.com>

On Fri, 12 Aug 2022, Mojca Miklavec via ntg-context wrote:

> Hi,
> 
> Hans helped me out with some asciidoc processing a while ago.
> 
> I played a bit further, but I'm currently facing two minor issues:
> 
> (a) I don't know how to turn program listing (verbatim code) from xml
> to (perhaps, vim-based) syntax highlighting (but most importantly, to
> make sure that line breaks work properly)

Does something like this work:

https://wiki.contextgarden.net/Verbatim_XML

Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-08-12 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 15:37 Mojca Miklavec via ntg-context
2022-08-12 21:20 ` Aditya Mahajan via ntg-context [this message]
2022-08-13  6:13   ` Mojca Miklavec via ntg-context
2022-08-13  6:15   ` Mojca Miklavec via ntg-context
2022-08-12 22:30 ` Max Chernoff via ntg-context

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=nycvar.YAK.7.78.908.2208121718560.280663@nqv-guvaxcnq \
    --to=ntg-context@ntg.nl \
    --cc=adityam@umich.edu \
    --cc=mojca.miklavec.lists@gmail.com \
    /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).