Error while updating to new beta
Hi, When compiling the format in the new beta, I get the following error: loading > ConTeXt File Macros / Job Handling ! LuaTeX error ...d/src/tex/texmf-context/tex/context/base/l-table.lua:106: C stack overflow stack traceback: ...d/src/tex/texmf-context/tex/context/base/l-table.lua:106: in function 'sortedkeys' ...d/src/tex/texmf-context/tex/context/base/l-table.lua:156: in function 'sortedpairs' .../src/tex/texmf-context/tex/context/base/data-pre.lua:168: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> ... .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/data-pre.lua:177: in function <.../src/tex/texmf-context/tex/context/base/data-pre.lua:165> .../src/tex/texmf-context/tex/context/base/file-job.lua:570: in function 'code' .../src/tex/texmf-context/tex/context/base/util-lua.lua:130: in function 'loadedluacode' .../src/tex/texmf-context/tex/context/base/luat-env.lua:285: in function 'luafilechunk' .../src/tex/texmf-context/tex/context/base/luat-cod.lua:45: in function 'registercode' <main ctx instance>:1: in main chunk. system > tex > error on line 20 in file /home/adityam/Software/context-pkgbuild/src/tex/texmf-context/tex/context/base/file-job.mkvi: LuaTeX error ... 10 %C This module is part of the \CONTEXT\ macro||package and is 11 %C therefore copyrighted by \PRAGMA. See mreadme.pdf for 12 %C details. 13 14 %D This module is still to be split and documented. 15 16 \writestatus{loading}{ConTeXt File Macros / Job Handling} 17 18 \unprotect 19 20 >> \registerctxluafile{file-job}{1.001} 21 22 % processing 23 24 \unexpanded\def\doifinputfileelse#name% 25 {\ctxcommand{doifinputfileelse("#name")}} 26 27 \unexpanded\def\processfile#name% 28 {\ctxcommand{processfile("#name")}} 29 30 % path control \registerctxluafile ...ua.registercode("#1","#2")} l.20 \registerctxluafile{file-job}{1.001} ? Aditya
On 15-10-2012 23:16, Aditya Mahajan wrote:
Hi,
When compiling the format in the new beta, I get the following error:
weird: I've added this to core-job local function toppath() local pathname = dirname(inputstack[#inputstack] or "") if pathname == "" then return "." else return pathname end end resolvers.toppath = topath resolvers.prefixes.toppath = function(str) return cleanpath(joinpath(toppath(),str)) end local function process(what,name) local depth = #typestack local process -- name = resolvers.resolve(name) but that should be harmless. (On my machine the format is made.) What if you comment name = resolvers.resolve(name) As it's only used in component etc code I wonder why it influences the format making 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, 15 Oct 2012, Hans Hagen wrote:
On 15-10-2012 23:16, Aditya Mahajan wrote:
Hi,
When compiling the format in the new beta, I get the following error:
weird: I've added this to core-job
local function toppath() local pathname = dirname(inputstack[#inputstack] or "") if pathname == "" then return "." else return pathname end end
resolvers.toppath = topath
resolvers.prefixes.toppath = function(str) return cleanpath(joinpath(toppath(),str)) end
local function process(what,name) local depth = #typestack local process -- name = resolvers.resolve(name)
but that should be harmless. (On my machine the format is made.)
What if you comment
name = resolvers.resolve(name)
Same error. But if I comment the definition of resolvers.prefixes.toppath, the error goes away. Aditya
On 16-10-2012 00:14, Aditya Mahajan wrote:
Same error. But if I comment the definition of resolvers.prefixes.toppath, the error goes away.
fixed (tested on opensuse and ubuntu) 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 -----------------------------------------------------------------
Same error. But if I comment the definition of resolvers.prefixes.toppath, the error goes away.
fixed (tested on opensuse and ubuntu)
The problem was that in some places there was a toppath with double "p" (pp) and in some places it was topath with single "p" (p). Will "toppath" be brought back? Cheers, André Caldas. -- - Por que altera a ordem natural da conversação! - Por que não? - Eu não gosto, não. - Você gosta quando copiam a mensagem original ao final do e-mail?
On 11/6/2012 10:04 PM, Andre Caldas wrote:
Same error. But if I comment the definition of resolvers.prefixes.toppath, the error goes away.
fixed (tested on opensuse and ubuntu)
The problem was that in some places there was a toppath with double "p" (pp) and in some places it was topath with single "p" (p).
Will "toppath" be brought back?
in only see double p's 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 -----------------------------------------------------------------
participants (3)
-
Aditya Mahajan -
Andre Caldas -
Hans Hagen