From: Aditya Mahajan <adityam@umich.edu>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Minimal code for exporting custom tags
Date: Mon, 18 May 2020 09:50:00 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YAK.7.77.849.2005180928510.225319@nqv-guvaxcnq> (raw)
In-Reply-To: <11099836-3176-676a-7ce4-365153e0579d@xs4all.nl>
On Mon, 18 May 2020, Hans Hagen wrote:
> On 5/18/2020 9:09 AM, Aditya Mahajan wrote:
>> Hi,
>>
>> What is needed to enable export of user defined macros? Consider the
>> following example:
>>
>> What am I missing in order to pass user-defined macros to the exporter?
> you're probably missing documentation + a high level define command
>
> This registers (extra) elements:
>
> \setelementbackendtag[mycommand]
> \setelementnature [mycommand][mixed]
>
Thanks! This also helped me find the documentation in hybrid.pdf.
I am not using a high-level interface because I was looking at how to get the output of `t-filter` and `t-vim` modules export correctly.
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-05-18 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 7:09 Aditya Mahajan
2020-05-18 9:34 ` Hans Hagen
2020-05-18 13:50 ` Aditya Mahajan [this message]
2020-05-18 17:31 ` Aditya Mahajan
2020-05-19 5:45 ` Aditya Mahajan
2020-05-19 6:16 ` Aditya Mahajan
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.77.849.2005180928510.225319@nqv-guvaxcnq \
--to=adityam@umich.edu \
--cc=j.hagen@xs4all.nl \
--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).