ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Jethro Djan via ntg-context <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Subject: Re: Command line arguments on context project
Date: Fri, 16 Dec 2022 17:49:04 +0100	[thread overview]
Message-ID: <f1264dfe-fae0-8d29-fce3-baf730492b61@gmail.com> (raw)
In-Reply-To: <6B1260C1-B936-4437-8A25-38191A4456C6@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1517 bytes --]

Jethro Djan via ntg-context schrieb am 16.12.2022 um 17:14:
> Dear list,
>
> I am using the project structure to typeset my thesis. This is how the 
> directory looks like:
>
> chapters/chapter1.tex
> chapters/chapter2.tex
> …
>
> output/
> env_thesis.tex
> prd_main.tex
> ref.bib
>
> I didn’t use the project.
>
> 1. How do I specify output directory?

context --runpath=output ...

> I have already seen the following thread:
>
> https://www.mail-archive.com/ntg-context@ntg.nl/msg101654.html
>
> It doesn’t seem to work on a project. So for example when I run mtxrun 
> —path=output --script context ../prd_main, I get this error:
>
> tex error on line 5 in file 
> /usr/local/texlive/2022/texmf-dist/doc/latex/buctthesis/chapter1.tex: 
> ! Undefined control sequence

How do you load the chapter file in your product file?

The error message above appears because ConTeXt can't find the chapter 
file of your document and uses one with the same name from a 
documentation of a LaTeX class which has the same name.

> 2. How do I get CoTeXt to recognise the ref.bib file when I run the 
> components not the product?
>
> For context, I don’t want the references printed at the end of each 
> chapter but I would like the in-text citation to work (if that is 
> possible). If not, is it possible compile the whole product but only 
> output a certain page range?

You need a reference to the environment file from within the component 
file, otherwise ConTeXt has no knowledge of the bib file.

Wolfgang


[-- Attachment #1.2: Type: text/html, Size: 3366 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
___________________________________________________________________________________

  reply	other threads:[~2022-12-16 16:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 16:14 Jethro Djan via ntg-context
2022-12-16 16:49 ` Wolfgang Schuster via ntg-context [this message]
2022-12-18 21:27 ` Alan Braslau via ntg-context
2022-12-19 15:01   ` Aditya Mahajan via ntg-context
2022-12-19 18:07     ` 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=f1264dfe-fae0-8d29-fce3-baf730492b61@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).