ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: Do environment files add implicit \starttext ... \stopttext
Date: Fri, 18 Nov 2022 16:15:15 +0100	[thread overview]
Message-ID: <b4fe3405-e8be-ccf6-9d8e-2957e91f2f9c@gmx.es> (raw)
In-Reply-To: <e36a3584-d6b4-2895-44c4-02a2957a819b@gmail.com>

On 11/18/22 15:52, Wolfgang Schuster via ntg-context wrote:
> Pablo Rodriguez via ntg-context schrieb am 15.11.2022 um 16:06:
>> [...]
>> It looks like when --environment is used, ConTeXt assumes that the main
>> source only contains text. Which makes sense (at least, to me).
> 
> The reason why this does work has nothing to do with the environment
> file, the only  thing which is responsible to get a PDF with output
> is the \setupbodyfont line.

Many thanks for your explanation, Wolfgang.

Now it is perfectly clear to me why this worked.

Many thanks for your 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
___________________________________________________________________________________

  reply	other threads:[~2022-11-18 15:15 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 [this message]
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=b4fe3405-e8be-ccf6-9d8e-2957e91f2f9c@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).