microtype error with lualatex: “attempt to call field warning a nil value”
no answer needed, I'm adding the question as reference
After todays update of luaotfload microtype
gives an error when used with lualatex:
documentclass{article}
usepackage{microtype}
begin{document}
abc
end{document}
leads to
/tex/latex/microtype/microtype.lua:145: attempt to call field 'warning' (a nil v
alue)
stack traceback:
...exlive/2018/texmf-dist/tex/latex/microtype/microtype.lua:145: in main chunk
[C]: in function 'require'
[directlua]:1: in main chunk.
l.59 MT@lua{require("microtype")}
luatex microtype
add a comment |
no answer needed, I'm adding the question as reference
After todays update of luaotfload microtype
gives an error when used with lualatex:
documentclass{article}
usepackage{microtype}
begin{document}
abc
end{document}
leads to
/tex/latex/microtype/microtype.lua:145: attempt to call field 'warning' (a nil v
alue)
stack traceback:
...exlive/2018/texmf-dist/tex/latex/microtype/microtype.lua:145: in main chunk
[C]: in function 'require'
[directlua]:1: in main chunk.
l.59 MT@lua{require("microtype")}
luatex microtype
add a comment |
no answer needed, I'm adding the question as reference
After todays update of luaotfload microtype
gives an error when used with lualatex:
documentclass{article}
usepackage{microtype}
begin{document}
abc
end{document}
leads to
/tex/latex/microtype/microtype.lua:145: attempt to call field 'warning' (a nil v
alue)
stack traceback:
...exlive/2018/texmf-dist/tex/latex/microtype/microtype.lua:145: in main chunk
[C]: in function 'require'
[directlua]:1: in main chunk.
l.59 MT@lua{require("microtype")}
luatex microtype
no answer needed, I'm adding the question as reference
After todays update of luaotfload microtype
gives an error when used with lualatex:
documentclass{article}
usepackage{microtype}
begin{document}
abc
end{document}
leads to
/tex/latex/microtype/microtype.lua:145: attempt to call field 'warning' (a nil v
alue)
stack traceback:
...exlive/2018/texmf-dist/tex/latex/microtype/microtype.lua:145: in main chunk
[C]: in function 'require'
[directlua]:1: in main chunk.
l.59 MT@lua{require("microtype")}
luatex microtype
luatex microtype
edited Feb 26 at 11:40
Ulrike Fischer
asked Feb 26 at 11:30
Ulrike FischerUlrike Fischer
194k8302688
194k8302688
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is due to a bug in microtype
. It uses an undefined lua-function, the bug appears now due as a side-effect of some changes in luaotfload
.
A work-around until microtype is fixed is to load luatexbase:
documentclass{article}
usepackage{luatexbase}
usepackage{microtype}
begin{document}
abc
end{document}
2
Oh no, right now texlive 2018 is frozen with this bug in it. I hope the texlive people can make an exception for this that breaks so many documents!
– pst
Feb 27 at 8:24
@UlrikeFischer I have exactly this problem! TL2018 should not have been frozen with this bug IMHO.
– Krishna
Feb 27 at 19:01
@Krishna it is not our bug, microtype must be corrected. I don't know if the author is reachable, I didn't get an answer to my mails.
– Ulrike Fischer
Feb 27 at 19:05
1
@Krishna then we would have had a broken luaotfload in texlive (the letterspacing didn't work). This would have been much worser.
– Ulrike Fischer
Feb 27 at 19:08
1
@Krishna no it broke from version 2.94 to 2.95, the problem was only there for around two weeks: github.com/u-fischer/luaotfload/issues/38.
– Ulrike Fischer
Feb 27 at 19:13
|
show 4 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f476740%2fmicrotype-error-with-lualatex-attempt-to-call-field-warning-a-nil-value%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is due to a bug in microtype
. It uses an undefined lua-function, the bug appears now due as a side-effect of some changes in luaotfload
.
A work-around until microtype is fixed is to load luatexbase:
documentclass{article}
usepackage{luatexbase}
usepackage{microtype}
begin{document}
abc
end{document}
2
Oh no, right now texlive 2018 is frozen with this bug in it. I hope the texlive people can make an exception for this that breaks so many documents!
– pst
Feb 27 at 8:24
@UlrikeFischer I have exactly this problem! TL2018 should not have been frozen with this bug IMHO.
– Krishna
Feb 27 at 19:01
@Krishna it is not our bug, microtype must be corrected. I don't know if the author is reachable, I didn't get an answer to my mails.
– Ulrike Fischer
Feb 27 at 19:05
1
@Krishna then we would have had a broken luaotfload in texlive (the letterspacing didn't work). This would have been much worser.
– Ulrike Fischer
Feb 27 at 19:08
1
@Krishna no it broke from version 2.94 to 2.95, the problem was only there for around two weeks: github.com/u-fischer/luaotfload/issues/38.
– Ulrike Fischer
Feb 27 at 19:13
|
show 4 more comments
This is due to a bug in microtype
. It uses an undefined lua-function, the bug appears now due as a side-effect of some changes in luaotfload
.
A work-around until microtype is fixed is to load luatexbase:
documentclass{article}
usepackage{luatexbase}
usepackage{microtype}
begin{document}
abc
end{document}
2
Oh no, right now texlive 2018 is frozen with this bug in it. I hope the texlive people can make an exception for this that breaks so many documents!
– pst
Feb 27 at 8:24
@UlrikeFischer I have exactly this problem! TL2018 should not have been frozen with this bug IMHO.
– Krishna
Feb 27 at 19:01
@Krishna it is not our bug, microtype must be corrected. I don't know if the author is reachable, I didn't get an answer to my mails.
– Ulrike Fischer
Feb 27 at 19:05
1
@Krishna then we would have had a broken luaotfload in texlive (the letterspacing didn't work). This would have been much worser.
– Ulrike Fischer
Feb 27 at 19:08
1
@Krishna no it broke from version 2.94 to 2.95, the problem was only there for around two weeks: github.com/u-fischer/luaotfload/issues/38.
– Ulrike Fischer
Feb 27 at 19:13
|
show 4 more comments
This is due to a bug in microtype
. It uses an undefined lua-function, the bug appears now due as a side-effect of some changes in luaotfload
.
A work-around until microtype is fixed is to load luatexbase:
documentclass{article}
usepackage{luatexbase}
usepackage{microtype}
begin{document}
abc
end{document}
This is due to a bug in microtype
. It uses an undefined lua-function, the bug appears now due as a side-effect of some changes in luaotfload
.
A work-around until microtype is fixed is to load luatexbase:
documentclass{article}
usepackage{luatexbase}
usepackage{microtype}
begin{document}
abc
end{document}
answered Feb 26 at 11:33
community wiki
Ulrike Fischer
2
Oh no, right now texlive 2018 is frozen with this bug in it. I hope the texlive people can make an exception for this that breaks so many documents!
– pst
Feb 27 at 8:24
@UlrikeFischer I have exactly this problem! TL2018 should not have been frozen with this bug IMHO.
– Krishna
Feb 27 at 19:01
@Krishna it is not our bug, microtype must be corrected. I don't know if the author is reachable, I didn't get an answer to my mails.
– Ulrike Fischer
Feb 27 at 19:05
1
@Krishna then we would have had a broken luaotfload in texlive (the letterspacing didn't work). This would have been much worser.
– Ulrike Fischer
Feb 27 at 19:08
1
@Krishna no it broke from version 2.94 to 2.95, the problem was only there for around two weeks: github.com/u-fischer/luaotfload/issues/38.
– Ulrike Fischer
Feb 27 at 19:13
|
show 4 more comments
2
Oh no, right now texlive 2018 is frozen with this bug in it. I hope the texlive people can make an exception for this that breaks so many documents!
– pst
Feb 27 at 8:24
@UlrikeFischer I have exactly this problem! TL2018 should not have been frozen with this bug IMHO.
– Krishna
Feb 27 at 19:01
@Krishna it is not our bug, microtype must be corrected. I don't know if the author is reachable, I didn't get an answer to my mails.
– Ulrike Fischer
Feb 27 at 19:05
1
@Krishna then we would have had a broken luaotfload in texlive (the letterspacing didn't work). This would have been much worser.
– Ulrike Fischer
Feb 27 at 19:08
1
@Krishna no it broke from version 2.94 to 2.95, the problem was only there for around two weeks: github.com/u-fischer/luaotfload/issues/38.
– Ulrike Fischer
Feb 27 at 19:13
2
2
Oh no, right now texlive 2018 is frozen with this bug in it. I hope the texlive people can make an exception for this that breaks so many documents!
– pst
Feb 27 at 8:24
Oh no, right now texlive 2018 is frozen with this bug in it. I hope the texlive people can make an exception for this that breaks so many documents!
– pst
Feb 27 at 8:24
@UlrikeFischer I have exactly this problem! TL2018 should not have been frozen with this bug IMHO.
– Krishna
Feb 27 at 19:01
@UlrikeFischer I have exactly this problem! TL2018 should not have been frozen with this bug IMHO.
– Krishna
Feb 27 at 19:01
@Krishna it is not our bug, microtype must be corrected. I don't know if the author is reachable, I didn't get an answer to my mails.
– Ulrike Fischer
Feb 27 at 19:05
@Krishna it is not our bug, microtype must be corrected. I don't know if the author is reachable, I didn't get an answer to my mails.
– Ulrike Fischer
Feb 27 at 19:05
1
1
@Krishna then we would have had a broken luaotfload in texlive (the letterspacing didn't work). This would have been much worser.
– Ulrike Fischer
Feb 27 at 19:08
@Krishna then we would have had a broken luaotfload in texlive (the letterspacing didn't work). This would have been much worser.
– Ulrike Fischer
Feb 27 at 19:08
1
1
@Krishna no it broke from version 2.94 to 2.95, the problem was only there for around two weeks: github.com/u-fischer/luaotfload/issues/38.
– Ulrike Fischer
Feb 27 at 19:13
@Krishna no it broke from version 2.94 to 2.95, the problem was only there for around two weeks: github.com/u-fischer/luaotfload/issues/38.
– Ulrike Fischer
Feb 27 at 19:13
|
show 4 more comments
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f476740%2fmicrotype-error-with-lualatex-attempt-to-call-field-warning-a-nil-value%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown