ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "H. van der Meer" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: Rebuilding the font cache: segmentation fault 11
Date: Sun, 22 Dec 2013 09:33:25 +0100	[thread overview]
Message-ID: <4DBF6B09-FE6A-4E3B-94C1-3CC80698EDBF@uva.nl> (raw)
In-Reply-To: <0B19DD6E-33D0-48A5-AA1F-8E156A284445@boede.nl>


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

Someone some time ago suggested this:

OSFONTDIR="$TEXMFHOME/dummy_for_fonts"
export OSFONTDIR

put it in your .bashrc folder or whatever shell you are using and make an empty folder dummy_for_fonts in $TEXMFHOME.

Hans van der Meer



On 22 dec. 2013, at 09:14, Willi Egger <context@boede.nl> wrote:

> That is also one of the thoughts I had… 
> For an intermediate solution, where can I disable the searching of the os-fonts, ie.disabling the OSFONTDIR variable?


[-- Attachment #1.2: Type: text/html, Size: 2586 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:[~2013-12-22  8:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-21 22:02 Willi Egger
2013-12-21 22:32 ` Hans Hagen
2013-12-22  8:14   ` Willi Egger
2013-12-22  8:33     ` H. van der Meer [this message]
2013-12-22  8:36       ` Willi Egger
2013-12-22 12:47       ` Willi Egger
2013-12-22 10:52 ` Wolfgang Schuster
2013-12-25 10:16   ` Keith J. Schultz
2013-12-25 16:27     ` Wolfgang Schuster

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=4DBF6B09-FE6A-4E3B-94C1-3CC80698EDBF@uva.nl \
    --to=h.vandermeer@uva.nl \
    --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).