From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: source code and result side by side
Date: Sun, 30 Jul 2017 19:13:36 +0200 [thread overview]
Message-ID: <31703445-47BA-4348-A20B-B4CCF4D5382F@fiee.net> (raw)
In-Reply-To: <alpine.LNX.2.20.1707281855110.27478@ybpnyubfg.ybpnyqbznva>
Am 2017-07-29 um 00:57 schrieb Aditya Mahajan <adityam@umich.edu>:
> On Fri, 28 Jul 2017, Henning Hraban Ramm wrote:
>
>> Ahoi again,
>>
>> I’m preparing some ConTeXt docs with a lot of examples and would like to reproduce what we have in the wiki as
>>
>> <context source="yes">
>> ...
>> </context>
>>
>> i.e. sourcecode beside the result.
>>
>> Often the shown source is exactly what I want to show, in other cases I need some additional setup that I don’t want to show.
>>
>> Which approach would you suggest? Combinations?
>
> \startbuffer[example-1]
> ....
> \stopbuffer
>
>
> \placesidebyside
> {\typebuffer[example-1]}
> {\getbuffer[setups, example-1]}
Thank you again, that should be enough for most of my small examples.
I guess I never heard of or forgot about \placesidebyside as well as \placeontopofeachother.
But I’d like to show a lot of similar examples to explain several options.
Therefore, if I’d like to simplify my code, but this doesn’t work:
\def\CodeExample#1{%
\startbuffer[zB]
#1
\stopbuffer
\typebuffer[zB]
\getbuffer[zB]
}
\CodeExample{\framed[frame=off,leftframe=on,rulethickness=1em,framecolor=blue]{Klotz am Bein}}
Compilation just stops, maybe some infinite loop?
Simpler:
\def\CodeExample#1{%
\startTEX
#1
\stopTEX
#1
}
Stops with the error:
Use of \m_syst_action_yes doesn't match its definition
Greetlings, Hraban
---
http://www.fiee.net
http://wiki.contextgarden.net
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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:[~2017-07-30 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 20:34 Henning Hraban Ramm
2017-07-28 22:57 ` Aditya Mahajan
2017-07-29 8:58 ` Pablo Rodriguez
2017-07-29 10:46 ` Pablo Rodriguez
2017-07-30 17:13 ` Henning Hraban Ramm [this message]
2017-07-30 18:43 ` Pablo Rodriguez
2017-07-31 1:26 ` Aditya Mahajan
2017-08-03 19:35 ` Henning Hraban Ramm
2017-08-03 19:46 ` Henning Hraban Ramm
[not found] ` <d7f4de09-e6d8-950b-5a98-6cab8195f959@gmail.com>
2017-08-04 10:32 ` Henning Hraban Ramm
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=31703445-47BA-4348-A20B-B4CCF4D5382F@fiee.net \
--to=texml@fiee.net \
--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).