From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Subject: Re: Do environment files add implicit \starttext ... \stopttext
Date: Wed, 16 Nov 2022 18:45:15 +0100 [thread overview]
Message-ID: <7df97c4c-5c69-0754-cd03-896b6638381a@gmail.com> (raw)
In-Reply-To: <406fe736fe764a359a33ea605652b8cb@unibe.ch>
[-- Attachment #1.1: Type: text/plain, Size: 989 bytes --]
Denis Maier via ntg-context schrieb am 15.11.2022 um 13:22:
>
> Hi,
>
> if I process an XML buffer, I’ve noticed I need to wrap the
> \xmlprocessbuffer in a \starttext ... \stoptext pair.
>
> [...]
>
> However, if I have the XML and the setups in dedicated files, there
> seems to be no need for \starttext ... \stoptext.
>
> [...]
>
> Running
>
> context text.xml –environment=setups.tex
>
> gives me a proper PDF without errors.
>
> Therefore my question:
>
> Does the use –environment automatically wrap the processed file in
> \starttext ... stoptext ?
>
> If not, what’s the reason for this behaviour? Am I missing something?
>
ConTeXt uses the file extension to decide who it should handle document,
in your case the extension is xml and the file is processed as
\starttext
\xmlprocess{main}{...}{}
\stoptext
The same thing happens when you have CLD document and use cld as file
extension.
For more details you can look at the processjob function in cont-run.lmt.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 3101 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2022-11-16 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 12:22 Denis Maier via ntg-context
2022-11-15 15:06 ` Pablo Rodriguez via ntg-context
2022-11-16 9:30 ` Denis Maier via ntg-context
2022-11-18 14:52 ` Wolfgang Schuster via ntg-context
2022-11-18 15:15 ` Pablo Rodriguez via ntg-context
2022-11-16 17:45 ` Wolfgang Schuster via ntg-context [this message]
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=7df97c4c-5c69-0754-cd03-896b6638381a@gmail.com \
--to=ntg-context@ntg.nl \
--cc=wolfgang.schuster.lists@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).