From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: wiki: debian installation
Date: Thu, 05 Oct 2006 05:47:09 +0100 [thread overview]
Message-ID: <E1GVL8X-0000vM-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Wed, 04 Oct 2006 02:02:17 +0200." <6faad9f00610031702w35081171s93bbb3cca02bfd88@mail.gmail.com>
> > Warning: pdfetex (file /home/myuser/texmf/fonts/map/dvipdfm/
> > context/original-base.map): invalid entry for `fmvr8x': font
> > file missing
>
> Some time ago it was a hot topic on the mailing list. See:
> http://wiki.contextgarden.net/Error_Recovery
> and fix it if possible even if it is working now for some reason.
I ran into the same issue a few days ago and eventually found my to
the same solution. About the 'some reason': I noticed that without
the fix, sometimes it worked, sometimes it didn't. The answer is the
damn database file (the ls-R). kpathsea searches in 'directory
order', which you can find with 'ls -U'. So
ls -U ~/texmf/fonts/map/
gave me pdfetex, dvips, then dvipdfm, and I couldn't understand why
anyway the dvipdfm file was being found ahead of the pdfetex one (even
without the $progname). The answer is that the ls-R file is listed
in, well, ls -R order, which is not necessarily directory order. It's
probably alphabetical. So dvipdfm is ahead of pdfetex. Getting rid
of the ls-R means the pdfetex map file is found (good), but it can
easily change back if some script makes a new ls-R (so it's not
robust).
Short version: Do the recommended fix.
-Sanjoy
`Never underestimate the evil of which men of power are capable.'
--Bertrand Russell, _War Crimes in Vietnam_, chapter 1.
next prev parent reply other threads:[~2006-10-05 4:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 19:24 plink
2006-09-30 2:41 ` Sanjoy Mahajan
2006-10-02 20:29 ` plink
2006-10-02 22:52 ` Sanjoy Mahajan
2006-10-03 16:26 ` itemize and placefigure plink
2006-10-04 0:15 ` Mojca Miklavec
2006-10-04 20:35 ` plink
2006-10-04 0:02 ` wiki: debian installation Mojca Miklavec
2006-10-04 20:28 ` plink
2006-10-05 4:47 ` Sanjoy Mahajan [this message]
2006-10-05 4:21 ` Sanjoy Mahajan
2006-10-05 4:48 ` Aditya Mahajan
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=E1GVL8X-0000vM-00@skye.ra.phy.cam.ac.uk \
--to=sanjoy@mrao.cam.ac.uk \
--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).