summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/web2c
diff options
context:
space:
mode:
authorMojca Miklavec <mojca.miklavec@gmail.com>2023-03-11 21:00:25 +0000
committerMojca Miklavec <mojca.miklavec@gmail.com>2023-03-11 21:00:25 +0000
commitbd5f31bb35702541bb4bec1b2baebcbe0c819cb0 (patch)
treef5010460144a7bee0cda0f7b3b4597967d130664 /Master/texmf-dist/web2c
parentd1fde8e3b4d1398c86dcca013fcc8b40f0a6a558 (diff)
Update ConTeXt
git-svn-id: svn://tug.org/texlive/trunk@66546 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/web2c')
-rw-r--r--Master/texmf-dist/web2c/texmfcnf.lua233
1 files changed, 161 insertions, 72 deletions
diff --git a/Master/texmf-dist/web2c/texmfcnf.lua b/Master/texmf-dist/web2c/texmfcnf.lua
index 9fd2d8e5988..dedadd1965a 100644
--- a/Master/texmf-dist/web2c/texmfcnf.lua
+++ b/Master/texmf-dist/web2c/texmfcnf.lua
@@ -1,79 +1,98 @@
--- public domain
+-- todo: come up with an auto-texlive identification (texmf-dist)
--- ConTeXt needs a properly expanded TEXMFLOCAL, so here is a
--- bit of lua code to make that happen
-
-local texmflocal = resolvers.prefixes.selfautoparent();
-texmflocal = string.gsub(texmflocal, "20%d%d$", "texmf-local");
+local hiddentexlivepath = ".texlive2023"
return {
type = "configuration",
- version = "1.1.0",
- date = "2012-05-24",
- time = "12:12:12",
- comment = "ConTeXt MkIV configuration file",
+ version = "1.1.3",
+ date = "2023-03-10", -- 2021-05-12 2011-06-02
+ time = "14:59:00",
+ comment = "ConTeXt MkIV and LMTX configuration file",
author = "Hans Hagen, PRAGMA-ADE, Hasselt NL",
+ target = "texlive",
content = {
- -- Originally there was support for engines and progname but I don't expect
- -- other engines to use this file, so first engines were removed. After that
- -- if made sense also to get rid of progname. At some point specific formats
- -- will be supported but then as a subtable with fallbacks, which sounds more
- -- natural. Also, at some point the paths will become tables. For the moment
- -- I don't care too much about it as extending is easy.
+ -- Originally there was support for engines and progname but I don't expect other engines to
+ -- use this file, so first engines were removed. After that if made sense also to get rid of
+ -- progname. In principle we could support multiple formats here (using subtables) but time
+ -- has demonstrated that we only have one format (the original ideas was to make a base layer
+ -- but I don't see it being used to it would be waste of time). So, after a decade it was
+ -- time to prune and update this file, also because LMTX has a few more features.
variables = {
- -- The following variable is predefined (but can be overloaded) and in
- -- most cases you can leve this one untouched. The built-in definition
- -- permits relocation of the tree.
+ -- The following variable is predefined (but can be overloaded) and in most cases you can
+ -- leave this one untouched. The built-in definition permits relocation of the tree.
--
- -- TEXMFCNF = "{selfautodir:,selfautoparent:}{,{/share,}/texmf{-local,}/web2c}"
+ -- if this_is_texlive then
+ -- resolvers.luacnfspec = 'selfautodir:;selfautoparent:;{selfautodir:,selfautoparent:}{/share,}/texmf{-local,}/web2c'
+ -- else
+ -- resolvers.luacnfspec = 'home:texmf/web2c;selfautoparent:texmf{-local,-context,}/web2c'
+ -- end
--
- -- more readable than "selfautoparent:{/texmf{-local,}{,/web2c},}}" is:
+ -- more readable is:
--
-- TEXMFCNF = {
- -- "selfautoparent:/texmf-local",
- -- "selfautoparent:/texmf-local/web2c",
- -- "selfautoparent:/texmf-dist",
- -- "selfautoparent:/texmf/web2c",
- -- "selfautoparent:",
+ -- "home:texmf/web2c,
+ -- "selfautoparent:texmf-local/web2c",
+ -- "selfautoparent:texmf-context/web2c",
+ -- "selfautoparent:texmf/web2c",
-- }
- -- only used for FONTCONFIG_PATH & TEXMFCACHE in TeX Live
+ -- We have only one cache path but there can be more. The first writable one will be taken
+ -- but there can be more readable paths.
- TEXMFSYSVAR = "selfautoparent:texmf-var",
- TEXMFVAR = "home:.texlive2023/texmf-var",
+ -- standalone:
+
+ -- TEXMFCACHE = "$SELFAUTOPARENT/texmf-cache",
- -- We have only one cache path but there can be more. The first writable one
- -- will be chosen but there can be more readable paths.
+ -- texlive
+ TEXMFVAR = "home:" .. hiddentexlivepath .. "/texmf-var",
+ TEXMFCONFIG = "home:" .. hiddentexlivepath .. "/texmf-config",
+ TEXMFSYSVAR = "selfautoparent:texmf-var",
TEXMFCACHE = "$TEXMFSYSVAR;$TEXMFVAR",
- TEXMFCONFIG = "home:.texlive2023/texmf-config",
- -- I don't like this texmf under home and texmf-home would make more
- -- sense. One never knows what installers put under texmf anywhere and
- -- sorting out problems will be a pain. But on the other hand ... home
- -- mess is normally under the users own responsibility.
+ -- I don't like this texmf under home and texmf-home would make more sense. One never knows
+ -- what installers put under texmf anywhere and sorting out problems will be a pain. But on
+ -- the other hand ... home mess is normally the users own responsibility.
--
- -- By using prefixes we don't get expanded paths in the cache __path__
- -- entry. This makes the tex root relocatable.
+ -- By using prefixes we don't get expanded paths in the cache __path__ entry. This makes the
+ -- tex root relocatable.
TEXMFOS = "selfautodir:",
- TEXMFDIST = "selfautoparent:texmf-dist",
- TEXMFLOCAL = texmflocal,
+ -- standalone:
+
+ -- TEXMFSYSTEM = "selfautoparent:texmf-$SELFAUTOSYSTEM",
+ -- TEXMFMAIN = "selfautoparent:texmf",
+ -- TEXMFCONTEXT = "selfautoparent:texmf-context",
+ -- TEXMFMODULES = "selfautoparent:texmf-modules",
+
+ -- texlive:
+
+ TEXMFDIST = "selfautoparent:texmf-dist",
TEXMFSYSCONFIG = "selfautoparent:texmf-config",
+
+ -- The texmf-local path is only used for (maybe) some additional configuration file.
+
+ TEXMFLOCAL = "selfautoparent:texmf-local",
TEXMFFONTS = "selfautoparent:texmf-fonts",
TEXMFPROJECT = "selfautoparent:texmf-project",
TEXMFHOME = "home:texmf",
-- TEXMFHOME = os.name == "macosx" and "home:Library/texmf" or "home:texmf",
- -- We need texmfos for a few rare files but as I have a few more bin trees
- -- a hack is needed. Maybe other users also have texmf-platform-new trees.
+ -- We need texmfos for a few rare files but as I have a few more bin trees a hack is needed.
+ -- Maybe other users also have texmf-platform-new trees, but so far I've never heard of it.
+
+ -- standalone:
+
+ -- TEXMF = "{$TEXMFHOME,!!$TEXMFPROJECT,!!$TEXMFFONTS,!!$TEXMFLOCAL,!!$TEXMFMODULES,!!$TEXMFCONTEXT,!!$TEXMFSYSTEM,!!$TEXMFMAIN}",
+
+ -- texlive:
TEXMF = "{$TEXMFCONFIG,$TEXMFHOME,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFPROJECT,!!$TEXMFFONTS,!!$TEXMFLOCAL,!!$TEXMFDIST}",
@@ -81,11 +100,11 @@ return {
ENCFONTS = ".;$TEXMF/fonts/data//;$TEXMF/fonts/enc/{dvips,pdftex}//",
VFFONTS = ".;$TEXMF/fonts/{data,vf}//",
TFMFONTS = ".;$TEXMF/fonts/{data,tfm}//",
+ PKFONTS = ".;$TEXMF/fonts/{data,pk}//",
T1FONTS = ".;$TEXMF/fonts/{data,type1}//;$OSFONTDIR",
AFMFONTS = ".;$TEXMF/fonts/{data,afm}//;$OSFONTDIR",
TTFONTS = ".;$TEXMF/fonts/{data,truetype}//;$OSFONTDIR",
OPENTYPEFONTS = ".;$TEXMF/fonts/{data,opentype}//;$OSFONTDIR",
- CMAPFONTS = ".;$TEXMF/fonts/cmap//",
FONTFEATURES = ".;$TEXMF/fonts/{data,fea}//;$OPENTYPEFONTS;$TTFONTS;$T1FONTS;$AFMFONTS",
FONTCIDMAPS = ".;$TEXMF/fonts/{data,cid}//",
OFMFONTS = ".;$TEXMF/fonts/{data,ofm,tfm}//",
@@ -101,12 +120,12 @@ return {
PYTHONINPUTS = ".;$TEXMF/scripts/context/python",
RUBYINPUTS = ".;$TEXMF/scripts/context/ruby",
LUAINPUTS = ".;$TEXINPUTS;$TEXMF/scripts/context/lua//",
- CLUAINPUTS = ".;$SELFAUTOLOC/lib/{context,luatex,}/lua//",
+ CLUAINPUTS = ".;$SELFAUTOLOC/lib/$engine//",
-- Not really used by MkIV so they might go away.
- BIBINPUTS = ".;$TEXMF/bibtex/bib//",
- BSTINPUTS = ".;$TEXMF/bibtex/bst//",
+ BIBINPUTS = ".;$TEXMF/bibtex/bib//;$TEXMF/tex/context//",
+ BSTINPUTS = ".;$TEXMF/bibtex/bst//;$TEXMF/tex/context//",
-- Experimental
@@ -115,28 +134,65 @@ return {
-- A few special ones that will change some day.
FONTCONFIG_FILE = "fonts.conf",
+
+ -- standalone
+
+ -- FONTCONFIG_PATH = "$TEXMFSYSTEM/fonts/conf",
+
+ --texlive
+
FONTCONFIG_PATH = "$TEXMFSYSVAR/fonts/conf",
},
- -- We have a few reserved subtables. These control runtime behaviour. The
- -- keys have names like 'foo.bar' which means that you have to use keys
- -- like ['foo.bar'] so for convenience we also support 'foo_bar'.
+ -- We have a few reserved subtables. These control runtime behaviour. Some are frozen at
+ -- at startup time, others can be changed any time.
directives = {
- -- There are a few variables that determine the engines
- -- limits. Most will fade away when we close in on version 1.
-
- ["luatex.expanddepth"] = "10000", -- 10000
- ["luatex.hashextra"] = "100000", -- 0
- ["luatex.nestsize"] = "1000", -- 50
- ["luatex.maxinopen"] = "500", -- 15
- ["luatex.maxprintline"] = " 10000", -- 79
- ["luatex.maxstrings"] = "500000", -- 15000 -- obsolete
- ["luatex.paramsize"] = "25000", -- 60
- ["luatex.savesize"] = "50000", -- 4000
- ["luatex.stacksize"] = "10000", -- 300
+ -- The default settings are actually set at startup so the values below overload
+ -- them. You can also specify a plus field which will bump a value and in LMTX a
+ -- step field that sets the incremental allocation of memory (because there we don't
+ -- allocate all at once).
+
+ -- texconfig.max_print_line = 100000
+ -- texconfig.function_size = 32768
+ -- texconfig.properties_size = 10000
+
+ -- These are for luametatex:
+
+ ["luametatex.errorlinesize"] = { size = 250 }, -- max = 255
+ ["luametatex.halferrorlinesize"] = { size = 250 }, -- max = 255
+ ["luametatex.expandsize"] = { size = 10000 }, -- max = 1000000
+ ["luametatex.stringsize"] = { size = 500000, step = 100000 }, -- max = 2097151 -- number of strings
+ ["luametatex.poolsize"] = { size = 10000000, step = 1000000 }, -- max = 100000000 -- chars in string
+ ["luametatex.hashsize"] = { size = 250000, step = 100000 }, -- max = 2097151
+ ["luametatex.nodesize"] = { size = 50000000, step = 500000 }, -- max = 50000000
+ ["luametatex.tokensize"] = { size = 10000000, step = 250000 }, -- max = 10000000
+ ["luametatex.buffersize"] = { size = 10000000, step = 1000000 }, -- max = 100000000
+ ["luametatex.inputsize"] = { size = 100000, step = 10000 }, -- max = 100000 -- aka stack
+ ["luametatex.filesize"] = { size = 2000, step = 200 }, -- max = 2000
+ ["luametatex.nestsize"] = { size = 10000, step = 1000 }, -- max = 10000
+ ["luametatex.parametersize"] = { size = 100000, step = 10000 }, -- max = 100000
+ ["luametatex.savesize"] = { size = 500000, step = 10000 }, -- max = 500000
+ ["luametatex.fontsize"] = { size = 100000, step = 250 }, -- max = 100000
+ ["luametatex.languagesize"] = { size = 250, step = 250 }, -- max = 10000
+ ["luametatex.marksize"] = { size = 250, step = 50 }, -- max = 10000
+ ["luametatex.insertsize"] = { size = 250, step = 25 }, -- max = 250
+
+ -- These are for luatex:
+
+ ["luatex.errorline"] = 250,
+ ["luatex.halferrorline"] = 125,
+ ["luatex.expanddepth"] = 10000,
+ ["luatex.hashextra"] = 100000,
+ ["luatex.nestsize"] = 1000,
+ ["luatex.maxinopen"] = 500,
+ ["luatex.maxprintline"] = 10000,
+ ["luatex.maxstrings"] = 500000,
+ ["luatex.paramsize"] = 25000,
+ ["luatex.savesize"] = 100000,
+ ["luatex.stacksize"] = 100000,
-- A few process related variables come next.
@@ -146,35 +202,68 @@ return {
["system.compile.cleanup"] = "no", -- remove tma files
["system.compile.strip"] = "yes", -- strip tmc files
- -- The io modes are similar to the traditional ones. Possible values
- -- are all, paranoid and restricted.
+ -- The io modes are similar to the traditional ones. Possible values are all, paranoid
+ -- and restricted.
["system.outputmode"] = "restricted",
["system.inputmode"] = "any",
- -- The following variable is under consideration. We do have protection
- -- mechanims but it's not enabled by default.
+ -- The following variable is under consideration. We do have protection mechanims but
+ -- it's not enabled by default.
["system.commandmode"] = "any", -- any none list
["system.commandlist"] = "mtxrun, convert, inkscape, gs, imagemagick, curl, bibtex, pstoedit",
- -- The mplib library support mechanisms have their own
- -- configuration. Normally these variables can be left as
- -- they are.
+ -- The mplib library support mechanisms have their own configuration. Normally these
+ -- variables can be left as they are.
["mplib.texerrors"] = "yes",
- -- Normally you can leave the font related directives untouched
- -- as they only make sense when testing.
+ -- Normally you can leave the font related directives untouched as they only make sense
+ -- when testing.
-- ["fonts.autoreload"] = "no",
- -- ["fonts.otf.loader.method"] = "table", -- table mixed sparse
-- ["fonts.otf.loader.cleanup"] = "0", -- 0 1 2 3
-- In an edit cycle it can be handy to launch an editor. The
-- preferred one can be set here.
- -- ["pdfview.method"] = "okular", -- default (often acrobat) xpdf okular
+ -- ["pdfview.method"] = "sumatra",
+
+ -- ["system.engine"] = "luajittex",
+ -- ["fonts.usesystemfonts"] = false,
+ -- ["modules.permitunprefixed"] = false,
+ -- ["resolvers.otherwise"] = false,
+
+ -- Sandboxing has been available for a while but is probably never used to maybe that mechanism
+ -- should be removed some day. Normally you will configure this in a local configuration file. By
+ -- default we are rather permissive. The next list comes from my machine:
+
+ -- ["system.rootlist"] = { "/data" }, -- { { "/data", "read" }, ... }
+
+ -- ["system.executionmode"] = "list", -- none | list | all
+ -- ["system.executionlist"] = {
+ -- "context",
+ -- "bibtex", "mlbibcontext",
+ -- "curl",
+ -- "gswin64c", "gswin32c", "gs",
+ -- "gm", "graphicmagick",
+ -- "pdftops",
+ -- "pstoedit",
+ -- "inkscape",
+ -- "woff2_decompress",
+ -- "hb-shape",
+ -- },
+ --
+ -- ["system.librarymode"] = "list", -- none | list | all
+ -- ["system.librarylist"] = {
+ -- "mysql",
+ -- "sqlite3",
+ -- "libharfbuzz", "libharfbuzz-0",
+ -- },
+ -- -- ["system.librarynames"] = {
+ -- -- ["libcurl"] = { "libcurl", "libcurl-4" },
+ -- -- },
},