From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Project structure with nested subfolders and shared environments.
Date: Fri, 16 Dec 2022 10:54:51 +0100 [thread overview]
Message-ID: <bd71c070-068f-b2d2-db36-8c25f986513e@fiee.net> (raw)
In-Reply-To: <CADUDiDH39p_uicYvVVNi9-O7kcRsrgXyFg=N8WZEWXCx6NK-7Q@mail.gmail.com>
Am 16.12.22 um 10:09 schrieb Pawel Urbanski via ntg-context:
> When I compile a document I switch to the SubSubFolder for the document
> file is in there.
In my experience this won’t work. ConTeXt searches from the current
folder (you can configure search paths, but I gave up on that, and you’d
have to do it in the called file).
It should be enough to call the environment from the project, but either
the project or the environment isn’t found if the path doesn’t fit the
call location.
Hraban
___________________________________________________________________________________
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-12-16 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 21:52 Pawel Urbanski via ntg-context
2022-12-16 6:51 ` Henning Hraban Ramm via ntg-context
2022-12-16 9:09 ` Pawel Urbanski via ntg-context
2022-12-16 9:54 ` Henning Hraban Ramm via ntg-context [this message]
2022-12-16 10:00 ` Pawel Urbanski via ntg-context
2022-12-16 10:19 ` Denis Maier via ntg-context
2022-12-16 14:00 ` Wolfgang Schuster via ntg-context
2022-12-16 9:11 ` Denis Maier 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=bd71c070-068f-b2d2-db36-8c25f986513e@fiee.net \
--to=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).