Re: [NTG-context] \typefile with a file in \usepath fails

30 Apr 2006


      On Sun, 30 Apr 2006 18:59:53 +0200, Hans Hagen  wrote:
...
nico wrote:
...
On Sun, 30 Apr 2006 15:22:49 +0200, Hans Hagen  wrote:
...
...
...
what version of context do you run? i though that i added support for
that some time ago
Version 2006.04.27.
\dodotypefile checks where the file is, but a following call to
\makelocreadfilename seems to set improperly \readfilename, but I'm  
not
sure to understand correctly the code.
it's
\makelocreadfilename{#3}%
that does the search
With the following patch it works: the \filepath found is used to expand  
the filename. \makelocreadfilename is still used, but i don't understand  
its role.

\def\dodotypefile[#1][#2]#3%
   {\bgroup
    \let\currenttypingclass\??tp
    \edef\currenttyping{#1}%
    \typingparameter\c!before
    \doiflocfileelse{#3}
      \donetrue % sets \readfilename
      {\doifinputfileelse{#3}
         {\donetrue\def\readfilename{\pathplusfile{\filepath}{#3}}} % here  
the filename is absolute
         \donefalse}%
    \ifdone
      \startpacked % includes \bgroup
       \dosetuptypelinenumbering{#2}%
       \doifinset{\typingparameter\c!option}{\v!commands,\v!slanted,\v!normal}
         {\setuptyping[#1][\c!option=\v!none]}%
       \doif{\typingparameter\c!option}\v!color
         {\expandafter\aftersplitstring#3\at.\to\prettyidentifier
          \settypingparameter\c!option{\prettyidentifier}}%
       \initializetyping
       \startverbatimcolor
       % still use this macro, but applied to \readfilename instead of #3
       \makelocreadfilename{\readfilename}%
       \doifundefinedelse{\currenttypingclass#3\v!global\c!start}
       ...

Now it can wait a real fix :-)

Regards,
BG