ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re:  Typesetting Markdown – Part 5: Interpolation
Date: Mon, 8 Jul 2019 10:13:04 -0700	[thread overview]
Message-ID: <CAANrE7oQ4i5diCKY5rcHXrCoMZmK5tm4pDkaj_=WJN8uNSPFdA@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.76.1907071512000.13567@nqv-guvaxcnq>


[-- Attachment #1.1: Type: text/plain, Size: 1810 bytes --]

Thanks again for the great ideas. The downside is that it comes with a lot
of extra ConTeXt setup code. My understanding is that the toc parameter to
pandoc only works when creating a standalone document. I think
\def\completecontent\empty is a bit more expressive of intent than
\def\completecontent{}. Modes are probably the way to go, though.

Thank you.

On Sun, Jul 7, 2019 at 12:18 PM Aditya Mahajan <adityam@umich.edu> wrote:

>
> On Sun, 7 Jul 2019, Thangalin wrote:
>
> > Thank you Aditya.
> >
> > The main.tex file is meant to be reusable for different document styles.
> By
> > removing \completecontent altogether from the main template, it would
> > preclude a different document from reusing the main.tex template with a
> > table of contents. I'd like the template to be "reusable"; making
> > modifications to "main.tex" --- or creating a copy --- would subvert that
> > goal.
>
> Pandoc allows that. For example, see line 140 of the default context
> template:
>
> https://github.com/jgm/pandoc-templates/blob/master/default.context
>
> I don't remember the exact command line parameters for pandoc that set
> the toc flag to true.
>
> An equivalent method will be to control this using a ConTeXt mode.
> Redefining \completecontent to \empty seems too drastic.
>
> Aditya
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to
> the Wiki!
>
> maillist : ntg-context@ntg.nl /
> http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : http://contextgarden.net
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 2885 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

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

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

  reply	other threads:[~2019-07-08 17:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-06 19:08 Thangalin
2019-07-07 14:17 ` Aditya Mahajan
2019-07-07 18:58   ` Thangalin
2019-07-07 19:17     ` Aditya Mahajan
2019-07-08 17:13       ` Thangalin [this message]
     [not found] <mailman.406.1562572373.1354.ntg-context@ntg.nl>
2019-07-08 18:26 ` Andres Conrado
2019-07-09 18:06   ` Thangalin
     [not found] <mailman.442.1562695595.1354.ntg-context@ntg.nl>
2019-07-09 19:22 ` Andres Conrado

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='CAANrE7oQ4i5diCKY5rcHXrCoMZmK5tm4pDkaj_=WJN8uNSPFdA@mail.gmail.com' \
    --to=thangalin@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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).