ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jin-Hwan Cho <chofchof@ktug.or.kr>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Struggling with luatools and MacTeX
Date: Wed, 28 May 2008 06:37:47 +0900	[thread overview]
Message-ID: <D8E8C779-C3C6-412B-8CE5-3106C489691F@ktug.or.kr> (raw)
In-Reply-To: <483C197D.4000002@wxs.nl>

On May 27, 2008, at 11:23 PM, Hans Hagen wrote:

> Jin-Hwan Cho wrote:
>> On May 27, 2008, at 6:49 PM, Hans Hagen wrote:
>>
>>> Jin-Hwan Cho wrote:
>>>> On May 27, 2008, at 5:21 PM, Taco Hoekwater wrote:
>>>>
>>>>> Jin-Hwan Cho wrote:
>>>>>> Still luatools cmr10.tfm does not work. But luatools cmr10.tfm*
>>>>>> works.
>>>>>> Is it intended?
>>>>> luatools cmr10.tfm works for me (linux). It could be a Mac thing
>>>>> (\r vs \n) but I have no idea how to test that.
>>>> I checked the function input.aux.find_file() in luatools.lua.
>>>>
>>>> In the 4309th line (for _, path in pairs(pathlist) do) the variable
>>>> "path" was
>>>>
>>>> !!/usr/local/texlive/2007/texmf-dist
>>>>
>>>> when "path" indicates the texmf tree having cmr10.tfm.
>>>>
>>>> Here, it did not end with "//" so that the variable recurse became
>>>> "false".
>>>> After I changed the value of "recurse" explicitly to "true", I  
>>>> could
>>>> get the
>>>> right result.
>>>>
>>>> Do you know exact reason?
>>> // indicates that the tree should be searched recursively
>>
>> In my case, the variable "path" shows the name of the directories
>> written in $TEXMF of texmf.cnf. Of course, every path does not end
>> with "//". But everyone thinks that file must be searched recursively
>> for these directories.
>>
>> In my opinion, the following line is non-sense.
>>
>> if path:find("//$") then recurse = true  else recurse = false end
>
> well, the !! as well as // are kind of standard web2c / tds / whatever

Finally I found what caused the problem just for me. My "texmf.cnf" had
the following line:

TEXMFHOME=$HOME/share/texmf-hyperref;$HOME/share/texmf-context

After replacing the character ";" to "," I had no problem.

Thanks again, ChoF.
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2008-05-27 21:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25 23:08 Jin-Hwan Cho
2008-05-26  8:58 ` Hans Hagen
2008-05-26 22:00   ` Jin-Hwan Cho
2008-05-27  7:35     ` Hans Hagen
2008-05-27  8:21     ` Taco Hoekwater
2008-05-27  9:17       ` Jin-Hwan Cho
2008-05-27  9:49         ` Hans Hagen
2008-05-27 14:17           ` Jin-Hwan Cho
2008-05-27 14:23             ` Hans Hagen
2008-05-27 21:37               ` Jin-Hwan Cho [this message]

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=D8E8C779-C3C6-412B-8CE5-3106C489691F@ktug.or.kr \
    --to=chofchof@ktug.or.kr \
    --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).