From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Parallel output of source data
Date: Tue, 03 Jul 2018 09:07:23 +0200 [thread overview]
Message-ID: <5B3B20AB.5080409@gmail.com> (raw)
In-Reply-To: <op.zlkddnvf62epfj@lpr>
[-- Attachment #1.1: Type: text/plain, Size: 2216 bytes --]
Hi Lukas,
when you create the buffer with the grabbufferdata-command you already set
the delimiter for the environment with the third argument, in the
example below
this is the \stopcontentexport command.
To have different start/stop-commands for your environment means you have
to change all names in the implementation of the contentxport-environment.
%%%%%%
\unexpanded\def\bH{....}
\def\dobH[#1]%
{...
\grabbufferdata[...][bH][eH]}
\def\eH
{....}
%%%%%%
Wolfgang
> Procházka Lukáš Ing. <mailto:LPr@pontex.cz>
> 3. Juli 2018 um 08:52
> Hello,
>
> I tried to \let shortcuts for \startcontentexport and
> \stopcontentexport, but Ctx run fails.
>
> I guess this is a basic misunderstanding, but - why?
>
> ----
> \unexpanded\def\startcontentexport{\dosingleempty\dostartcontentexport}
>
> \def\dostartcontentexport[#1]%
> {\iffirstargument
> \edef\contentexportfile{#1}%
> \else
> \let\contentexportfile\empty
> \fi
> \grabbufferdata[contentexport][startcontentexport][stopcontentexport]
> }
>
> \def\stopcontentexport{%
>
> \doifsomething{\contentexportfile}{\savebuffer[list=contentexport,prefix=no,file=\contentexportfile]}%
>
> \getbufferdata[contentexport]
> }
>
> \let\bX=\startcontentexport % <---- Use of these two "shortcuts" is
> not possible,
> \let\eX=\stopcontentexport % <---- I'm getting : ! TeX capacity
> exceeded, sorry [input stack size=10000]
>
> \starttext
>
> A
>
> \startcontentexport[t~.out.mkiv]
> Hello!
> \startitemize
> \item Item
> \stopitemize
> \stopcontentexport
>
> B
>
> \bX[t2~.out.mkiv]
> Ahoj
> \eX
>
> \stoptext
> ----
>
> HSo how to define "shortcuts" properly?
>
> Best regards,
>
> Lukas
>
>
> ___________________________________________________________________________________
> 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: 3874 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-07-03 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 7:10 Procházka Lukáš Ing.
2016-12-02 19:04 ` Wolfgang Schuster
2016-12-05 7:26 ` Procházka Lukáš Ing.
2018-07-03 6:52 ` Procházka Lukáš Ing.
2018-07-03 7:07 ` Wolfgang Schuster [this message]
2018-07-03 14:39 ` Procházka Lukáš Ing.
2018-07-03 7:11 ` Hans Hagen
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=5B3B20AB.5080409@gmail.com \
--to=schuster.wolfgang@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).