ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Matt Gushee <matt@gushee.net>
To: "ConTeXt users' mailing list" <ntg-context@ntg.nl>
Subject: No output for no apparent reason
Date: Sun, 2 Aug 2015 23:52:05 -0600	[thread overview]
Message-ID: <CABrD0ecUkrRtPAiaYec+JCx4U1rAiQn4qCD14cPAEQmgiTQTZQ@mail.gmail.com> (raw)


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

Hello, ConTeXt people--

I am coming back to ConTeXt after a long absence (for about the 3rd or 4th
time - maybe if I just stuck with it I wouldn't keep having these problems,
eh?).

I have a new installation of the standalone ConTeXt package on an Arch
Linux system. I obtained the 'first-setup.sh' script according to
instructions, then ran:

    ./first-setup.sh --modules=all --engine=luatex --context=current

 I also have TeXlive, including ConTeXt, installed as a regular Arch
package; however, I don't intend to use it. In any case, I have sourced
/opt/context/tex/setuptex, so I have:

    $ which context
    /opt/context/tex/texmf-linux-64/bin/context

    $ context --version
    mtx-context     | ConTeXt Process Management 0.61
    mtx-context     |
    mtx-context     | main context file:
/opt/context/tex/texmf-context/tex/context/base/context.mkiv
    mtx-context     | current version: 2015.05.18 12:26

I have tried the "hello world" example described on the wiki, and the
output from that is exactly as expected, but I am having trouble with a
couple of projects that I created in 2006. Each project is moderately
complex, including an environment file and several product files. Each
project produced output in the past. But now I run 'context <file>', and
there are no obvious errors (except for fonts not found, but in that case
the default font should be used instead, correct?), yet no PDF is produced.

Furthermore, the log files say that PDF files were generated, e.g.:

    mkiv lua stats  > result saved in file: hobo.pdf, compresslevel 3,
objectcompresslevel 3

And yes, I've checked the modification times on the log files, and they are
up to date.

Of course I am not giving very much detail, but I have no idea what might
be relevant. Any ideas about how to troubleshoot this?

Thanks,
Matt Gushee

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

             reply	other threads:[~2015-08-03  5:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03  5:52 Matt Gushee [this message]
2015-08-03  7:18 ` Wolfgang Schuster
2015-08-03 14:36   ` Matt Gushee

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=CABrD0ecUkrRtPAiaYec+JCx4U1rAiQn4qCD14cPAEQmgiTQTZQ@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).