Ok, thanks. I understand the mktexlsr stuff is nothing serious. But the "! Math error: parameter \Umathquad\displaystyle is not set." is very serious. I tried several things, as mtxrun --generate ; context --make en". Nothing good. I thought I remembered something about an opentype font euler.otf. But putting it somewhere in one of the font folders and regenerating doesn't work either. I getting a bit nervous now.... Hans van der Meer On 27 jun 2011, at 20:31, luigi scarso wrote:

On Mon, Jun 27, 2011 at 8:24 PM, Hans van der Meer wrote:

...

The ! Math error: parameter \Umathquad\displaystyle is not set. came up again.

Therefore decided to get new beta. Now suddenly I get on the console what seem literaly hundredsds of thousands messages mktexlsr: : not a directory, skipping. Has there been an infinite loop been crept in somewhere?

Used the scripts that always worked, nothing new. See email with Subject "problem running first-setup.sh" -- luigi

Some more experimenting did the trick, finally. (I must not forget to document it well this time ;-) (1) the opentypefont euler.otf in font-tree, accessible by ConTeXt. (2) mtxrun --script fonts --reload Then I can regenerate the format and get good ConTeXt runs again. As to the cause of this. I dug up a mail-exchange with Taco Hoekwater, him telling me there was some leftover reference to this euler.otf font that was unnecessary. I have mailed him, to ask if he can remove that reference. Hans van der Meer On 27 jun 2011, at 21:25, luigi scarso wrote:

On Mon, Jun 27, 2011 at 8:42 PM, Hans van der Meer wrote:

...

Ok, thanks. I understand the mktexlsr stuff is nothing serious.

But the "! Math error: parameter \Umathquad\displaystyle is not set." is very serious. I tried several things, as mtxrun --generate ; context --make en". Nothing good. I thought I remembered something about an opentype font euler.otf. Latest minimals has still the mktexlsr error, but I'm not able to reproduce "! Math error: parameter \Umathquad\displaystyle is not set." --- do you have an example ? -- luigi

---

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 ___________________________________________________________________________________

On 27-6-2011 8:42, Hans van der Meer wrote:

Ok, thanks. I understand the mktexlsr stuff is nothing serious.

But the "! Math error: parameter \Umathquad\displaystyle is not set." is very serious. I tried several things, as mtxrun --generate ; context --make en". Nothing good. I thought I remembered something about an opentype font euler.otf. But putting it somewhere in one of the font folders and regenerating doesn't work either. I getting a bit nervous now....

What is your font definition? do you define a proper math font? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

On Mon, Jun 27, 2011 at 10:38 PM, Hans Hagen wrote:

On 27-6-2011 8:42, Hans van der Meer wrote:

...

Ok, thanks. I understand the mktexlsr stuff is nothing serious.

it looks like mktexlsr has a bug

- when run with "" on windows it tries to hash / - when run on linux with "" it loops

any unknown path does this

so, i think that maybe when there is an empty path given or in the texmf spec, that this problem surfaces

Hans

-----------------------------------------------------------------                                          Hans Hagen | PRAGMA ADE              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands    tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com                                             | www.pragma-pod.nl ----------------------------------------------------------------- ___________________________________________________________________________________ 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 ___________________________________________________________________________________

imo, a shift is missed

From line 73 of mktexlsr, look at # ADD THIS below

# A copy of some stuff from mktex.opt, so we can run in the presence of # terminally damaged ls-R files. while test $# -gt 0; do if test "x$1" = x--help || test "x$1" = x-help; then echo "$usage" exit 0 elif test "x$1" = x--version || test "x$1" = x-version; then echo "`basename $0` $version" kpsewhich --version exit 0 elif test "x$1" = x--verbose || test "x$1" = x-verbose; then verbose=true elif test "x$1" = x--dry-run || test "x$1" = x-n; then dry_run=true elif test "x$1" = x--quiet || test "x$1" = x--silent \ || test "x$1" = x-quiet || test "x$1" = x-silent ; then verbose=false elif test "x$1" = x--; then : elif echo "x$1" | grep '^x-' >/dev/null; then echo "$progname: unknown option \`$1', try --help if you need it." >&2 exit 1 else if test ! -d "$1"; then echo "$progname: $1: not a directory, skipping." >&2 shift ## ADD THIS, otherwise a loop continue fi # By saving the argument in a file, we can later get it back while # supporting spaces in the name. This still doesn't support # newlines in the directory names, but nobody ever complains about # that, and it seems much too much trouble to use \0 terminators. (umask 077 if echo "$1" >>"$treefile"; then :; else echo "$progname: $treefile: could not append to arg file, goodbye." >&2 exit 1 fi ) fi shift done -- luigi

On Mon, Jun 27, 2011 at 11:26 PM, Hans Hagen wrote:

On 27-6-2011 11:05, luigi scarso wrote:

imo, a shift is missed

...

From line 73 of mktexlsr, look at # ADD THIS below

Can you find out what the complete path spec is that is used for the loop? (It looks like TEXMFDBS is used .. I wonder why not TEXMF as it makes no sense to use another variable.)

The bug doesn't depend to TEXMFDBS: without the shift the input args are never consumed. The next time the while is executed, the same condition on the path is checked again and found true (i.e. it doesn't exist).

The path spec are or a treefile rooted on ${TMPDIR/tmp} or, if it doesn't exist , the paths given by kpsewhich --show-path=ls-R -- luigi