From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Denis Maier via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: Do environment files add implicit \starttext ... \stopttext
Date: Tue, 15 Nov 2022 16:06:58 +0100 [thread overview]
Message-ID: <ccfe34dc-5e1d-8f83-3b5c-71095b15b112@gmx.es> (raw)
In-Reply-To: <406fe736fe764a359a33ea605652b8cb@unibe.ch>
On 11/15/22 13:22, Denis Maier via ntg-context wrote:
> 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.
> []
> Therefore my question:
>
> Does the use –environment automatically wrap the processed file in
> \starttext ... stoptext ?
Hi Denis,
try a source file with this contents:
\ConTeXt\ is great.
with the following environment:
\setuppapersize[A6]
\setupbodyfont[pagella]
It looks like when --environment is used, ConTeXt assumes that the main
source only contains text. Which makes sense (at least, to me).
Just in case it might help,
Pablo
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-11-15 15:06 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 [this message]
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
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=ccfe34dc-5e1d-8f83-3b5c-71095b15b112@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).