From: Matt Gushee <matt@gushee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: No output for no apparent reason
Date: Mon, 3 Aug 2015 08:36:55 -0600 [thread overview]
Message-ID: <CABrD0eeFNC7aJQCoRt-MktA4OrQEb1SD9G233B8xLhuVfhtxyA@mail.gmail.com> (raw)
In-Reply-To: <55BF15AE.4060503@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 699 bytes --]
Hi, Wolfgang--
On Mon, Aug 3, 2015 at 1:18 AM, Wolfgang Schuster <
schuster.wolfgang@gmail.com> wrote:
> Is it possible that your main file of your document is a project?
>
> When this is the case change this file to a product and all subfiles into
> components.
>
Yes, that was the problem. And I can see there are a few other things I
need to change, but the project was nowhere near finished anyway, and at
least I now have output.
By the way, shouldn't there be an error or at least a warning when ConTeXt
can't produce output? At the very least, the log file should not report
that a PDF file was saved when it was not. This seems like a bug.
Thanks for your quick reply!
--
Matt Gushee
[-- Attachment #1.2: Type: text/html, Size: 1172 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2015-08-03 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 5:52 Matt Gushee
2015-08-03 7:18 ` Wolfgang Schuster
2015-08-03 14:36 ` Matt Gushee [this message]
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=CABrD0eeFNC7aJQCoRt-MktA4OrQEb1SD9G233B8xLhuVfhtxyA@mail.gmail.com \
--to=matt@gushee.net \
--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).