ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pol Stra <ryzz@hotmail.fr>
To: ntg-context@ntg.nl
Subject: Re: Project structure
Date: Sun, 9 Feb 2014 12:25:49 +0100	[thread overview]
Message-ID: <BLU0-SMTP4780E8A3CCD8FDC5A001F60B1910@phx.gbl> (raw)
In-Reply-To: <20140206212505.GE3631@homerow>

Le jeudi 6 février 2014, 22:25:05 Marco Patzer a écrit :
> On 2014–02–05 pol stra wrote:
> > The problem is that only text of first introduction is used.
> 
> You can use \allinputpaths to see what's going on. The paths are
> indeed added and ConTeXt walks through the list and uses a matching
> file, if found. This happens to always be the file of the first
> chapter.
> 
> I don't know know of a command which resets the custom set up paths.
> If none exists, I doubt it will be hard to implement.
> 
> > I attached the project structure.
> 
> Thanks for that.
> 
> Marco

So, if I well understood, their is currently no solution but give a different 
name for each file?

___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2014-02-09 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DUB124-W7A61A44931264E38D65CDB1950@phx.gbl>
2014-02-05 10:21 ` pol stra
2014-02-06 21:25   ` Marco Patzer
2014-02-09 11:25     ` Pol Stra [this message]
2014-07-26  9:01 project structure Hans Hagen
2014-07-27 11:24 ` Procházka Lukáš Ing. - Pontex s. r. o.
2014-07-27 13:59   ` Hans Hagen

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=BLU0-SMTP4780E8A3CCD8FDC5A001F60B1910@phx.gbl \
    --to=ryzz@hotmail.fr \
    --cc=ntg-context@ntg.nl \
    /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).