ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Schmitz Thomas A." <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: MacOsX Mavericks and Luatex
Date: Thu, 24 Oct 2013 09:01:10 +0200	[thread overview]
Message-ID: <E3AF668C-0549-4D10-B207-B05FC45E9C4D@uni-bonn.de> (raw)
In-Reply-To: <DF489A49-7C73-489E-BEED-F7610FD32D83@me.com>


On 24 Oct 2013, at 07:41, Pierre Bovet <pierre67@me.com> wrote:

> Hi all!
> 
> It seems that Luatex (0.76 2013/04/05) don't works with Mavericks?
> 
> Thank's in advanced for your help and testimonies
> 
> Best wishes

I’m afraid you’re right! I installed Mavericks yesterday; trying to build the format, I get this:

fonts           > names > globbing path '/Library/Fonts/**.ttf'
mtx-context     | fatal error: no return code, message: luatex: execution interrupted

It may be a new wacky font in /Library/Fonts. But so far, I have not been able to unset OSFONTDIR and make context ignore this directory. (Unlike some people in a recent discussion, my preference would be to NOT include any system fonts by default: it slows rebuilding the formats down, people who want it can achieve it, and it’s generally a bad idea). I’ll see if I can figure out how to do this and will report back, but for the time being, context cannot be used on Mavericks…

Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2013-10-24  7:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  5:41 Pierre Bovet
2013-10-24  6:03 ` Schmitz Thomas A.
2013-10-24  7:01 ` Schmitz Thomas A. [this message]
2013-10-24  7:12   ` Schmitz Thomas A.
2013-10-24 14:17     ` Hans Hagen
2013-10-24 14:28       ` Alan BRASLAU
2013-10-24 14:39       ` Schmitz Thomas A.
2013-10-24 14:44         ` Aditya Mahajan
2013-10-24 22:01           ` Schmitz Thomas A.
2013-10-24 22:13             ` Hans Hagen
2013-10-24 22:33               ` Aditya Mahajan
2013-10-25  7:30               ` Meer, H. van der
2016-05-19 14:26               ` MacOsX OSFONTDIR environment variable Meer, Hans van der
2013-10-24 21:40         ` MacOsX Mavericks and Luatex Hans Hagen
2013-10-24  7:04 ` Wolfgang Schuster
2013-10-24  7:13   ` Schmitz Thomas A.
2013-10-24  7:24     ` Wolfgang Schuster
2013-10-24  7:30       ` Pierre Bovet
2013-10-24  7:36         ` Wolfgang Schuster
2013-10-24  7:45           ` Pierre Bovet
2013-10-24  8:00             ` Wolfgang Schuster
2013-10-24  8:08               ` Schmitz Thomas A.
2013-10-24  8:31                 ` Pierre Bovet
2013-10-24  9:56               ` Keith J. Schultz
2013-10-24 22:17                 ` Hans Hagen
2013-10-25  8:49               ` Taco Hoekwater
2013-10-25 13:01                 ` Otared Kavian
2013-10-24  9:13 ` Keith J. Schultz

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=E3AF668C-0549-4D10-B207-B05FC45E9C4D@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --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).