ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: compiling project files
Date: Sun, 13 Aug 2006 17:46:04 +0200	[thread overview]
Message-ID: <6faad9f00608130846y5f576cd8m20731846953cc08f@mail.gmail.com> (raw)
In-Reply-To: <221cc89e0608122039vb9709e3oc232ffd2f00f011c@mail.gmail.com>

On 8/13/06, Derek Schmidt wrote:
> Aditya,
>
> Sorry it took so long to get back to you. I've only just had a chance
> to try this now.
>
> The .tuo file for the _product_ file shows the files being loaded.
> Compiling the _project_ file yields no .tuo. My product file does
> indeed look like what you wrote.
>
> Shall I jump out the window or not? :)

It depends on which floor you live in ;)

It might help if you create a *minimal* example first (just a few
files with no more than the structure itself and a couple of
words/sections in it), write the commands that you use and attach a
zip with those files and probably logs.

Mojca

PS: try to update ConTeXt to the latest version if you intend to send
log files and try to use the ruby version of texexec ("texmfstart
texexec") if possible. None should be necessary (it should work with
the ancient version as well), but it often helps, esp. because tetex
still uses the "2002" version of ConTeXt for example.

  reply	other threads:[~2006-08-13 15:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09 15:52 Derek Schmidt
2006-08-09 16:26 ` Tobias Burnus
2006-08-09 16:27 ` Aditya Mahajan
2006-08-13  3:39   ` Derek Schmidt
2006-08-13 15:46     ` Mojca Miklavec [this message]
2006-08-14 20:44     ` Peter Münster
2006-08-15 20:16       ` Boris Tschirschwitz
2006-08-15 20:29         ` Aditya Mahajan
2006-08-16 15:58           ` Mojca Miklavec
2006-08-16 16:07             ` Taco Hoekwater
2006-08-16 22:52               ` 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=6faad9f00608130846y5f576cd8m20731846953cc08f@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).