From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: "N. Raghavendra" <nyraghu27132@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Including part of a program source file
Date: Sat, 21 Apr 2018 17:29:58 +0200 [thread overview]
Message-ID: <5ADB58F6.7080008@gmail.com> (raw)
In-Reply-To: <87zi1wpskq.fsf@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2168 bytes --]
The verbatim commands have a range key which let you select parts of the
code,
you can use line numbers to include a small block (e.g. range={3,10} or
range {3,+7})
or you put labels in your code.
\startbuffer
% cmd:one:begin
\define\FirstCommand
{\dosingleempty\doFirstCommand}
\def\doFirstCommand[#1]%
{This is the definition for the first command}
% cmd:one:end
% cmd:two:begin
\define\SecondCommand
{\dosingleempty\doSecondCommand}
\def\doSecondCommand[#1]%
{This is the definition for the second command}
% cmd:two:end
\stopbuffer
\starttext
\typebuffer[range={cmd:two:begin,cmd:two:end}]
\stoptext
Wolfgang
> N. Raghavendra <mailto:nyraghu27132@gmail.com>
> 21. April 2018 um 16:00
> I am writing some notes using ConTeXt, which involves displaying parts
> of some program source files. At present, I am manually cutting and
> pasting the parts into the ConTeXt file. Is it possible to make ConTeXt
> do that for me? I am thinking of including each part of the Coq sources
> between tags like this:
>
> ------------------------------------------------------------
> $ cat src-file
> <tag-1>
> part_to_be_included_1
> </tag-2>
>
> <tag-2>
> part_to_be_included_2
> </tag-2>
> ------------------------------------------------------------
>
> I would like to say something like
>
> \IncludePart{src-file}{tag-1}
>
> in my ConTeXt file to get
>
> part_to_be_included_1
>
> at that place in the PDF output after I run `context'. I would
> appreciate any advice on how to go about this.
>
> Thanks,
> Raghu.
>
> --
> N. Raghavendra <raghu@hri.res.in>, http://www.retrotexts.net/
> Harish-Chandra Research Institute, http://www.hri.res.in/
> ___________________________________________________________________________________
> 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: 4007 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-04-21 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 14:00 N. Raghavendra
2018-04-21 15:29 ` Wolfgang Schuster [this message]
2018-04-21 18:51 ` N. Raghavendra
2018-04-21 23:06 ` Alan Braslau
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=5ADB58F6.7080008@gmail.com \
--to=schuster.wolfgang@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=nyraghu27132@gmail.com \
/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).