From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Font memory issues ?
Date: Wed, 11 Jan 2006 09:16:07 +0100 [thread overview]
Message-ID: <43C4BEC7.1050102@wxs.nl> (raw)
In-Reply-To: <95E5C116-BA8D-42CC-A101-1B83BFEFD35B@trichotomic.net>
David Wooten wrote:
>
> On Jan 10, 2006, at 1:54 PM, Hans Hagen wrote:
>
>> did you remake the format after increasing the memory values?
>
>
> This means texexec --make --all ?
>
> I did try the above, but the numbers in the log when running my file
> do not change. I can only imagine that there is another place to
> change the memory settings. In my context.cnf, the numbers are
> identical to yours below, although I did try to raise the
> font.mem.size.context as we've been discussing.
ah, you need to set the values in texmf.cnf! context.cnf is just an
example (unless you point the TEXMFCNF environment variable to the
alternative cnf file)
Hans
next prev parent reply other threads:[~2006-01-11 8:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 19:07 David Wooten
2006-01-10 19:17 ` Font memory issues ? : bib-module? David Wooten
2006-01-10 20:22 ` Taco Hoekwater
2006-01-10 21:54 ` Font memory issues ? Hans Hagen
2006-01-11 0:39 ` David Wooten
2006-01-11 8:16 ` Hans Hagen [this message]
2006-01-11 23:17 ` David Wooten
2006-01-12 7:25 ` Thomas A. Schmitz
2006-01-12 8:28 ` Hans Hagen
2006-01-12 19:04 ` David Wooten
2006-01-12 20:02 ` Taco Hoekwater
2006-01-12 22:49 ` David Wooten
2006-01-13 0:15 ` Taco Hoekwater
2006-01-12 20:05 ` Hans Hagen
2006-01-12 22:48 ` David Wooten
2006-01-16 23:18 ` David Wooten
2006-01-17 10:15 ` Thomas A. Schmitz
2006-01-17 17:35 ` David Wooten
2006-01-17 18:31 ` Thomas A. Schmitz
2006-01-17 21:46 ` David Wooten
2006-01-17 22:36 ` Hans Hagen
2006-01-17 23:15 ` David Wooten
2006-01-19 19:41 ` David Wooten
2006-01-19 20:16 ` Taco Hoekwater
2006-01-19 20:28 ` Taco Hoekwater
2006-01-19 21:44 ` Hans Hagen
2006-01-19 22:37 ` Taco Hoekwater
2006-01-19 23:47 ` David Wooten
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=43C4BEC7.1050102@wxs.nl \
--to=pragma@wxs.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).