From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: source code and result side by side
Date: Sun, 30 Jul 2017 21:26:05 -0400 (EDT) [thread overview]
Message-ID: <alpine.OSX.2.02.1707302123280.48300@nqv-znpobbx> (raw)
In-Reply-To: <31703445-47BA-4348-A20B-B4CCF4D5382F@fiee.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2011 bytes --]
On Sun, 30 Jul 2017, Henning Hraban Ramm wrote:
> 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}}
You can't do that with buffers. If you need to define your own macros that
behave like buffers, you need to use \grabbufferdata (see buff-ini.mkiv).
But in this case, there is a simpler solution:
\defineframed
[CodeExampleFramed]
[
frame=off,
width=0.5\textwidth,
align=normal,
]
\definebuffer
[CodeExample]
\define\stopCodeExample
{\placesidebyside
{\CodeExampleFramed{\typeCodeExample}}
{\CodeExampleFramed{\getCodeExample}}}
\starttext
\startCodeExample
\framed
[
frame=off,
leftframe=on,
rulethickness=1em,
framecolor=blue,
]{Klotz am Bein}
\stopCodeExample
\stoptext
[-- 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:[~2017-07-31 1:26 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
2017-07-30 18:43 ` Pablo Rodriguez
2017-07-31 1:26 ` Aditya Mahajan [this message]
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=alpine.OSX.2.02.1707302123280.48300@nqv-znpobbx \
--to=adityam@umich.edu \
--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).