TeXLive Pretest 2018: beamer and subfig collide
27
documentclass{beamer}
usepackage{subfig}
begin{document}
test
end{document}
returns undefined control sequence
@@magyar@captionfix
(It was not so in January; I am on fully updated pretest)
beamer captions subfig
edited Apr 11 '18 at 23:57
David Carlisle
496k4111431890
asked Apr 11 '18 at 23:41
VictorVictor
13924
|
show 1 more comment
27
documentclass{beamer}
usepackage{subfig}
begin{document}
test
end{document}
returns undefined control sequence
@@magyar@captionfix
(It was not so in January; I am on fully updated pretest)
beamer captions subfig
edited Apr 11 '18 at 23:57
David Carlisle
496k4111431890
asked Apr 11 '18 at 23:41
VictorVictor
13924
1
github.com/josephwright/beamer/issues
– Henri Menke
Apr 11 '18 at 23:51
1
I'm voting to close this question as off-topic because TeX.SX is not an issue tracker.
– Henri Menke
Apr 11 '18 at 23:51
@HenriMenke why beamer, the code is in caption?
– David Carlisle
Apr 11 '18 at 23:54
12
@HenriMenke IMO that's not a good reason to close, for a few reasons: (1) I It's hard in general for a user, encountering some trouble with getting their work done, to know whether something is a real issue to be reported, or just something they ought to do differently, (2) Even if it seems a bug, the “proper place” to report is often not clear: is hard to know which package/code has an issue, (3) Even if it's a bug that can be reported at an issue tracker, usually users just want to learn a workaround from TeX experts so that they can continue getting their work done. So it's on-topic IMO.
– ShreevatsaR
Apr 11 '18 at 23:57
7
@HenriMenke the code is not in beamer or in subfig, it is in caption3.sty. As explained in the accepted answer of the meta question you linked to if the question is not clearly just a bug report on a known package there is merit in asking the question and answering it here
– David Carlisle
Apr 12 '18 at 0:19
|
show 1 more comment
27
27
27
1
documentclass{beamer}
usepackage{subfig}
begin{document}
test
end{document}
returns undefined control sequence
@@magyar@captionfix
(It was not so in January; I am on fully updated pretest)
beamer captions subfig
edited Apr 11 '18 at 23:57
David Carlisle
496k4111431890
asked Apr 11 '18 at 23:41
VictorVictor
13924
documentclass{beamer}
usepackage{subfig}
begin{document}
test
end{document}
returns undefined control sequence
@@magyar@captionfix
(It was not so in January; I am on fully updated pretest)
beamer captions subfig
beamer captions subfig
edited Apr 11 '18 at 23:57
David Carlisle
496k4111431890
asked Apr 11 '18 at 23:41
VictorVictor
13924
edited Apr 11 '18 at 23:57
David Carlisle
496k4111431890
asked Apr 11 '18 at 23:41
VictorVictor
13924
edited Apr 11 '18 at 23:57
David Carlisle
496k4111431890
edited Apr 11 '18 at 23:57
David Carlisle
496k4111431890
edited Apr 11 '18 at 23:57
David Carlisle
496k4111431890
496k4111431890
asked Apr 11 '18 at 23:41
VictorVictor
13924
asked Apr 11 '18 at 23:41
VictorVictor
13924
asked Apr 11 '18 at 23:41
VictorVictor
13924
13924
1
github.com/josephwright/beamer/issues
– Henri Menke
Apr 11 '18 at 23:51
1
I'm voting to close this question as off-topic because TeX.SX is not an issue tracker.
– Henri Menke
Apr 11 '18 at 23:51
@HenriMenke why beamer, the code is in caption?
– David Carlisle
Apr 11 '18 at 23:54
12
@HenriMenke IMO that's not a good reason to close, for a few reasons: (1) I It's hard in general for a user, encountering some trouble with getting their work done, to know whether something is a real issue to be reported, or just something they ought to do differently, (2) Even if it seems a bug, the “proper place” to report is often not clear: is hard to know which package/code has an issue, (3) Even if it's a bug that can be reported at an issue tracker, usually users just want to learn a workaround from TeX experts so that they can continue getting their work done. So it's on-topic IMO.
– ShreevatsaR
Apr 11 '18 at 23:57
7
@HenriMenke the code is not in beamer or in subfig, it is in caption3.sty. As explained in the accepted answer of the meta question you linked to if the question is not clearly just a bug report on a known package there is merit in asking the question and answering it here
– David Carlisle
Apr 12 '18 at 0:19
|
show 1 more comment
1
github.com/josephwright/beamer/issues
– Henri Menke
Apr 11 '18 at 23:51
1
I'm voting to close this question as off-topic because TeX.SX is not an issue tracker.
– Henri Menke
Apr 11 '18 at 23:51
@HenriMenke why beamer, the code is in caption?
– David Carlisle
Apr 11 '18 at 23:54
12
@HenriMenke IMO that's not a good reason to close, for a few reasons: (1) I It's hard in general for a user, encountering some trouble with getting their work done, to know whether something is a real issue to be reported, or just something they ought to do differently, (2) Even if it seems a bug, the “proper place” to report is often not clear: is hard to know which package/code has an issue, (3) Even if it's a bug that can be reported at an issue tracker, usually users just want to learn a workaround from TeX experts so that they can continue getting their work done. So it's on-topic IMO.
– ShreevatsaR
Apr 11 '18 at 23:57
7
@HenriMenke the code is not in beamer or in subfig, it is in caption3.sty. As explained in the accepted answer of the meta question you linked to if the question is not clearly just a bug report on a known package there is merit in asking the question and answering it here
– David Carlisle
Apr 12 '18 at 0:19
1
1
github.com/josephwright/beamer/issues
– Henri Menke
Apr 11 '18 at 23:51
github.com/josephwright/beamer/issues
– Henri Menke
Apr 11 '18 at 23:51
1
1
I'm voting to close this question as off-topic because TeX.SX is not an issue tracker.
– Henri Menke
Apr 11 '18 at 23:51
I'm voting to close this question as off-topic because TeX.SX is not an issue tracker.
– Henri Menke
Apr 11 '18 at 23:51
@HenriMenke why beamer, the code is in caption?
– David Carlisle
Apr 11 '18 at 23:54
@HenriMenke why beamer, the code is in caption?
– David Carlisle
Apr 11 '18 at 23:54
12
12
@HenriMenke IMO that's not a good reason to close, for a few reasons: (1) I It's hard in general for a user, encountering some trouble with getting their work done, to know whether something is a real issue to be reported, or just something they ought to do differently, (2) Even if it seems a bug, the “proper place” to report is often not clear: is hard to know which package/code has an issue, (3) Even if it's a bug that can be reported at an issue tracker, usually users just want to learn a workaround from TeX experts so that they can continue getting their work done. So it's on-topic IMO.
– ShreevatsaR
Apr 11 '18 at 23:57
@HenriMenke IMO that's not a good reason to close, for a few reasons: (1) I It's hard in general for a user, encountering some trouble with getting their work done, to know whether something is a real issue to be reported, or just something they ought to do differently, (2) Even if it seems a bug, the “proper place” to report is often not clear: is hard to know which package/code has an issue, (3) Even if it's a bug that can be reported at an issue tracker, usually users just want to learn a workaround from TeX experts so that they can continue getting their work done. So it's on-topic IMO.
– ShreevatsaR
Apr 11 '18 at 23:57
7
7
@HenriMenke the code is not in beamer or in subfig, it is in caption3.sty. As explained in the accepted answer of the meta question you linked to if the question is not clearly just a bug report on a known package there is merit in asking the question and answering it here
– David Carlisle
Apr 12 '18 at 0:19
@HenriMenke the code is not in beamer or in subfig, it is in caption3.sty. As explained in the accepted answer of the meta question you linked to if the question is not clearly just a bug report on a known package there is merit in asking the question and answering it here
– David Carlisle
Apr 12 '18 at 0:19
|
show 1 more comment
3 Answers
3
active
oldest
votes
30
It is enough to add a definition of the command to relax
documentclass{beamer}
usepackage{subfig}
makeatletter
let@@magyar@captionfixrelax
makeatother
begin{document}
test
end{document}
This is due to a change to @ifundefined in the 2018 LaTeX release.
caption3.sty has
@ifundefined{@@magyar@captionfix}AtBeginDocument@firstofone{%
g@addto@macro@@magyar@captionfix{%
letcaption@lfmt@simple@magyarcaption@lfmt@simpleMagyar
letcaption@lfmt@simpleMagyarcaption@lfmt@default@magyar}}
which relies on the side effect that @ifundefined defines the tested command to be relax. That side effect is almost always unwanted and in the 2018 LaTeX release this is changed, as noted in LaTeX News 28. I have mailed the author suggesting
@ifundefined{@@magyar@captionfix}%
{let@@magyar@captionfix@emptyAtBeginDocument}
@firstofone
{%
g@addto@macro@@magyar@captionfix{%
letcaption@lfmt@simple@magyarcaption@lfmt@simpleMagyar
letcaption@lfmt@simpleMagyarcaption@lfmt@default@magyar}}
answered Apr 11 '18 at 23:53
David CarlisleDavid Carlisle
496k4111431890
2
Wow,@ifundefinedchanged... While I perfectly understand the reason behind, this is a pretty fundamental kernel macro that now behaves differently. I am afraid we are going to see a lot of similar version clashes for a long time.
– Daniel
Apr 12 '18 at 6:17
3
@Daniel we see clashes all the time here (and before that on c.t.t) with one package doingifxfoo@undefinedand it working until another package does@ifundefined{foo}there are really very few legitimate cases where a package intentionally uses the implicitlettorelaxintentionally (we found two and changed them before the release) the use here missed our search but the previous behaviour, although it avoided an error here was clearly accidental, it defined@@magyar@captionfixto be an infinite loop
– David Carlisle
Apr 12 '18 at 6:57
1
That is good to know and I don‘t question the reasons behind (your example how one undefined test changes the outcome of another is more than convincing...). In fact, I truely trust you guys in this respect. My comment was more about the general tragedy behind having to fix fundamentally flawed behavior in some API that nevertheless has a widespread use. It always is a dilemma.
– Daniel
Apr 13 '18 at 5:24
add a comment |
8
This bug has been fixed in https://github.com/axelsommerfeldt/caption/commit/e03e61eb7c5987644cb1d8ed336dbb5e8ee2f96f and should be included version v1.7-167 of the caption3 package
2
Uploaded to CTAN on 2018-04-15
– Axel Sommerfeldt
May 1 '18 at 10:55
add a comment |
3
Given what samcarter and Axel Sommerfeldt report above, that the bug has been fixed and put on the CTAN, you may want to consider updating the caption library files, and for that matter, freshen all your installed LaTeX files. If you have a TexLive installation, the way to do this is given here, namely, from the command line: sudo tlmgr update --self, then sudo tlmgr update --all. I did this and it fixed the problem.
answered Jun 14 '18 at 21:40
Andrew SundstromAndrew Sundstrom
1586
Then either you already have TL 2018 or you are still using an earlier edition. Note that the question concerned the pre-test and was posted in April .... Can you update using this command from pre-test to release?
– cfr
Jun 15 '18 at 3:20
@cfr Yes, I already had TexLive-2018 installed and ran into this bug. But I’m afraid I don’t know how to do what you suggest.
– Andrew Sundstrom
Jun 15 '18 at 3:26
add a comment |
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
});
}
});
draft saved
draft discarded
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%2f426088%2ftexlive-pretest-2018-beamer-and-subfig-collide%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
30
It is enough to add a definition of the command to relax
documentclass{beamer}
usepackage{subfig}
makeatletter
let@@magyar@captionfixrelax
makeatother
begin{document}
test
end{document}
This is due to a change to @ifundefined in the 2018 LaTeX release.
caption3.sty has
@ifundefined{@@magyar@captionfix}AtBeginDocument@firstofone{%
g@addto@macro@@magyar@captionfix{%
letcaption@lfmt@simple@magyarcaption@lfmt@simpleMagyar
letcaption@lfmt@simpleMagyarcaption@lfmt@default@magyar}}
which relies on the side effect that @ifundefined defines the tested command to be relax. That side effect is almost always unwanted and in the 2018 LaTeX release this is changed, as noted in LaTeX News 28. I have mailed the author suggesting
@ifundefined{@@magyar@captionfix}%
{let@@magyar@captionfix@emptyAtBeginDocument}
@firstofone
{%
g@addto@macro@@magyar@captionfix{%
letcaption@lfmt@simple@magyarcaption@lfmt@simpleMagyar
letcaption@lfmt@simpleMagyarcaption@lfmt@default@magyar}}
answered Apr 11 '18 at 23:53
David CarlisleDavid Carlisle
496k4111431890
2
Wow,@ifundefinedchanged... While I perfectly understand the reason behind, this is a pretty fundamental kernel macro that now behaves differently. I am afraid we are going to see a lot of similar version clashes for a long time.
– Daniel
Apr 12 '18 at 6:17
3
@Daniel we see clashes all the time here (and before that on c.t.t) with one package doingifxfoo@undefinedand it working until another package does@ifundefined{foo}there are really very few legitimate cases where a package intentionally uses the implicitlettorelaxintentionally (we found two and changed them before the release) the use here missed our search but the previous behaviour, although it avoided an error here was clearly accidental, it defined@@magyar@captionfixto be an infinite loop
– David Carlisle
Apr 12 '18 at 6:57
1
That is good to know and I don‘t question the reasons behind (your example how one undefined test changes the outcome of another is more than convincing...). In fact, I truely trust you guys in this respect. My comment was more about the general tragedy behind having to fix fundamentally flawed behavior in some API that nevertheless has a widespread use. It always is a dilemma.
– Daniel
Apr 13 '18 at 5:24
add a comment |
30
It is enough to add a definition of the command to relax
documentclass{beamer}
usepackage{subfig}
makeatletter
let@@magyar@captionfixrelax
makeatother
begin{document}
test
end{document}
This is due to a change to @ifundefined in the 2018 LaTeX release.
caption3.sty has
@ifundefined{@@magyar@captionfix}AtBeginDocument@firstofone{%
g@addto@macro@@magyar@captionfix{%
letcaption@lfmt@simple@magyarcaption@lfmt@simpleMagyar
letcaption@lfmt@simpleMagyarcaption@lfmt@default@magyar}}
which relies on the side effect that @ifundefined defines the tested command to be relax. That side effect is almost always unwanted and in the 2018 LaTeX release this is changed, as noted in LaTeX News 28. I have mailed the author suggesting
@ifundefined{@@magyar@captionfix}%
{let@@magyar@captionfix@emptyAtBeginDocument}
@firstofone
{%
g@addto@macro@@magyar@captionfix{%
letcaption@lfmt@simple@magyarcaption@lfmt@simpleMagyar
letcaption@lfmt@simpleMagyarcaption@lfmt@default@magyar}}
answered Apr 11 '18 at 23:53
David CarlisleDavid Carlisle
496k4111431890
2
Wow,@ifundefinedchanged... While I perfectly understand the reason behind, this is a pretty fundamental kernel macro that now behaves differently. I am afraid we are going to see a lot of similar version clashes for a long time.
– Daniel
Apr 12 '18 at 6:17
3
@Daniel we see clashes all the time here (and before that on c.t.t) with one package doingifxfoo@undefinedand it working until another package does@ifundefined{foo}there are really very few legitimate cases where a package intentionally uses the implicitlettorelaxintentionally (we found two and changed them before the release) the use here missed our search but the previous behaviour, although it avoided an error here was clearly accidental, it defined@@magyar@captionfixto be an infinite loop
– David Carlisle
Apr 12 '18 at 6:57
1
That is good to know and I don‘t question the reasons behind (your example how one undefined test changes the outcome of another is more than convincing...). In fact, I truely trust you guys in this respect. My comment was more about the general tragedy behind having to fix fundamentally flawed behavior in some API that nevertheless has a widespread use. It always is a dilemma.
– Daniel
Apr 13 '18 at 5:24
add a comment |
30
30
30
It is enough to add a definition of the command to relax
documentclass{beamer}
usepackage{subfig}
makeatletter
let@@magyar@captionfixrelax
makeatother
begin{document}
test
end{document}
This is due to a change to @ifundefined in the 2018 LaTeX release.
caption3.sty has
@ifundefined{@@magyar@captionfix}AtBeginDocument@firstofone{%
g@addto@macro@@magyar@captionfix{%
letcaption@lfmt@simple@magyarcaption@lfmt@simpleMagyar
letcaption@lfmt@simpleMagyarcaption@lfmt@default@magyar}}
which relies on the side effect that @ifundefined defines the tested command to be relax. That side effect is almost always unwanted and in the 2018 LaTeX release this is changed, as noted in LaTeX News 28. I have mailed the author suggesting
@ifundefined{@@magyar@captionfix}%
{let@@magyar@captionfix@emptyAtBeginDocument}
@firstofone
{%
g@addto@macro@@magyar@captionfix{%
letcaption@lfmt@simple@magyarcaption@lfmt@simpleMagyar
letcaption@lfmt@simpleMagyarcaption@lfmt@default@magyar}}
answered Apr 11 '18 at 23:53
David CarlisleDavid Carlisle
496k4111431890
It is enough to add a definition of the command to relax
documentclass{beamer}
usepackage{subfig}
makeatletter
let@@magyar@captionfixrelax
makeatother
begin{document}
test
end{document}
This is due to a change to @ifundefined in the 2018 LaTeX release.
caption3.sty has
@ifundefined{@@magyar@captionfix}AtBeginDocument@firstofone{%
g@addto@macro@@magyar@captionfix{%
letcaption@lfmt@simple@magyarcaption@lfmt@simpleMagyar
letcaption@lfmt@simpleMagyarcaption@lfmt@default@magyar}}
which relies on the side effect that @ifundefined defines the tested command to be relax. That side effect is almost always unwanted and in the 2018 LaTeX release this is changed, as noted in LaTeX News 28. I have mailed the author suggesting
@ifundefined{@@magyar@captionfix}%
{let@@magyar@captionfix@emptyAtBeginDocument}
@firstofone
{%
g@addto@macro@@magyar@captionfix{%
letcaption@lfmt@simple@magyarcaption@lfmt@simpleMagyar
letcaption@lfmt@simpleMagyarcaption@lfmt@default@magyar}}
answered Apr 11 '18 at 23:53
David CarlisleDavid Carlisle
496k4111431890
edited Apr 12 '18 at 0:27
answered Apr 11 '18 at 23:53
David CarlisleDavid Carlisle
496k4111431890
answered Apr 11 '18 at 23:53
David CarlisleDavid Carlisle
496k4111431890
answered Apr 11 '18 at 23:53
David CarlisleDavid Carlisle
496k4111431890
496k4111431890
2
Wow,@ifundefinedchanged... While I perfectly understand the reason behind, this is a pretty fundamental kernel macro that now behaves differently. I am afraid we are going to see a lot of similar version clashes for a long time.
– Daniel
Apr 12 '18 at 6:17
3
@Daniel we see clashes all the time here (and before that on c.t.t) with one package doingifxfoo@undefinedand it working until another package does@ifundefined{foo}there are really very few legitimate cases where a package intentionally uses the implicitlettorelaxintentionally (we found two and changed them before the release) the use here missed our search but the previous behaviour, although it avoided an error here was clearly accidental, it defined@@magyar@captionfixto be an infinite loop
– David Carlisle
Apr 12 '18 at 6:57
1
That is good to know and I don‘t question the reasons behind (your example how one undefined test changes the outcome of another is more than convincing...). In fact, I truely trust you guys in this respect. My comment was more about the general tragedy behind having to fix fundamentally flawed behavior in some API that nevertheless has a widespread use. It always is a dilemma.
– Daniel
Apr 13 '18 at 5:24
add a comment |
2
Wow,@ifundefinedchanged... While I perfectly understand the reason behind, this is a pretty fundamental kernel macro that now behaves differently. I am afraid we are going to see a lot of similar version clashes for a long time.
– Daniel
Apr 12 '18 at 6:17
3
@Daniel we see clashes all the time here (and before that on c.t.t) with one package doingifxfoo@undefinedand it working until another package does@ifundefined{foo}there are really very few legitimate cases where a package intentionally uses the implicitlettorelaxintentionally (we found two and changed them before the release) the use here missed our search but the previous behaviour, although it avoided an error here was clearly accidental, it defined@@magyar@captionfixto be an infinite loop
– David Carlisle
Apr 12 '18 at 6:57
1
That is good to know and I don‘t question the reasons behind (your example how one undefined test changes the outcome of another is more than convincing...). In fact, I truely trust you guys in this respect. My comment was more about the general tragedy behind having to fix fundamentally flawed behavior in some API that nevertheless has a widespread use. It always is a dilemma.
– Daniel
Apr 13 '18 at 5:24
2
2
Wow,
@ifundefined changed... While I perfectly understand the reason behind, this is a pretty fundamental kernel macro that now behaves differently. I am afraid we are going to see a lot of similar version clashes for a long time.– Daniel
Apr 12 '18 at 6:17
Wow,
@ifundefined changed... While I perfectly understand the reason behind, this is a pretty fundamental kernel macro that now behaves differently. I am afraid we are going to see a lot of similar version clashes for a long time.– Daniel
Apr 12 '18 at 6:17
3
3
@Daniel we see clashes all the time here (and before that on c.t.t) with one package doing
ifxfoo@undefined and it working until another package does @ifundefined{foo} there are really very few legitimate cases where a package intentionally uses the implicit let to relax intentionally (we found two and changed them before the release) the use here missed our search but the previous behaviour, although it avoided an error here was clearly accidental, it defined @@magyar@captionfix to be an infinite loop– David Carlisle
Apr 12 '18 at 6:57
@Daniel we see clashes all the time here (and before that on c.t.t) with one package doing
ifxfoo@undefined and it working until another package does @ifundefined{foo} there are really very few legitimate cases where a package intentionally uses the implicit let to relax intentionally (we found two and changed them before the release) the use here missed our search but the previous behaviour, although it avoided an error here was clearly accidental, it defined @@magyar@captionfix to be an infinite loop– David Carlisle
Apr 12 '18 at 6:57
1
1
That is good to know and I don‘t question the reasons behind (your example how one undefined test changes the outcome of another is more than convincing...). In fact, I truely trust you guys in this respect. My comment was more about the general tragedy behind having to fix fundamentally flawed behavior in some API that nevertheless has a widespread use. It always is a dilemma.
– Daniel
Apr 13 '18 at 5:24
That is good to know and I don‘t question the reasons behind (your example how one undefined test changes the outcome of another is more than convincing...). In fact, I truely trust you guys in this respect. My comment was more about the general tragedy behind having to fix fundamentally flawed behavior in some API that nevertheless has a widespread use. It always is a dilemma.
– Daniel
Apr 13 '18 at 5:24
add a comment |
8
This bug has been fixed in https://github.com/axelsommerfeldt/caption/commit/e03e61eb7c5987644cb1d8ed336dbb5e8ee2f96f and should be included version v1.7-167 of the caption3 package
2
Uploaded to CTAN on 2018-04-15
– Axel Sommerfeldt
May 1 '18 at 10:55
add a comment |
8
This bug has been fixed in https://github.com/axelsommerfeldt/caption/commit/e03e61eb7c5987644cb1d8ed336dbb5e8ee2f96f and should be included version v1.7-167 of the caption3 package
2
Uploaded to CTAN on 2018-04-15
– Axel Sommerfeldt
May 1 '18 at 10:55
add a comment |
8
8
8
This bug has been fixed in https://github.com/axelsommerfeldt/caption/commit/e03e61eb7c5987644cb1d8ed336dbb5e8ee2f96f and should be included version v1.7-167 of the caption3 package
This bug has been fixed in https://github.com/axelsommerfeldt/caption/commit/e03e61eb7c5987644cb1d8ed336dbb5e8ee2f96f and should be included version v1.7-167 of the caption3 package
edited Apr 15 '18 at 21:08
community wiki
2 revs, 2 users 80%
samcarter
2
Uploaded to CTAN on 2018-04-15
– Axel Sommerfeldt
May 1 '18 at 10:55
add a comment |
2
Uploaded to CTAN on 2018-04-15
– Axel Sommerfeldt
May 1 '18 at 10:55
2
2
Uploaded to CTAN on 2018-04-15
– Axel Sommerfeldt
May 1 '18 at 10:55
Uploaded to CTAN on 2018-04-15
– Axel Sommerfeldt
May 1 '18 at 10:55
add a comment |
3
Given what samcarter and Axel Sommerfeldt report above, that the bug has been fixed and put on the CTAN, you may want to consider updating the caption library files, and for that matter, freshen all your installed LaTeX files. If you have a TexLive installation, the way to do this is given here, namely, from the command line: sudo tlmgr update --self, then sudo tlmgr update --all. I did this and it fixed the problem.
answered Jun 14 '18 at 21:40
Andrew SundstromAndrew Sundstrom
1586
Then either you already have TL 2018 or you are still using an earlier edition. Note that the question concerned the pre-test and was posted in April .... Can you update using this command from pre-test to release?
– cfr
Jun 15 '18 at 3:20
@cfr Yes, I already had TexLive-2018 installed and ran into this bug. But I’m afraid I don’t know how to do what you suggest.
– Andrew Sundstrom
Jun 15 '18 at 3:26
add a comment |
3
Given what samcarter and Axel Sommerfeldt report above, that the bug has been fixed and put on the CTAN, you may want to consider updating the caption library files, and for that matter, freshen all your installed LaTeX files. If you have a TexLive installation, the way to do this is given here, namely, from the command line: sudo tlmgr update --self, then sudo tlmgr update --all. I did this and it fixed the problem.
answered Jun 14 '18 at 21:40
Andrew SundstromAndrew Sundstrom
1586
Then either you already have TL 2018 or you are still using an earlier edition. Note that the question concerned the pre-test and was posted in April .... Can you update using this command from pre-test to release?
– cfr
Jun 15 '18 at 3:20
@cfr Yes, I already had TexLive-2018 installed and ran into this bug. But I’m afraid I don’t know how to do what you suggest.
– Andrew Sundstrom
Jun 15 '18 at 3:26
add a comment |
3
3
3
Given what samcarter and Axel Sommerfeldt report above, that the bug has been fixed and put on the CTAN, you may want to consider updating the caption library files, and for that matter, freshen all your installed LaTeX files. If you have a TexLive installation, the way to do this is given here, namely, from the command line: sudo tlmgr update --self, then sudo tlmgr update --all. I did this and it fixed the problem.
answered Jun 14 '18 at 21:40
Andrew SundstromAndrew Sundstrom
1586
Given what samcarter and Axel Sommerfeldt report above, that the bug has been fixed and put on the CTAN, you may want to consider updating the caption library files, and for that matter, freshen all your installed LaTeX files. If you have a TexLive installation, the way to do this is given here, namely, from the command line: sudo tlmgr update --self, then sudo tlmgr update --all. I did this and it fixed the problem.
answered Jun 14 '18 at 21:40
Andrew SundstromAndrew Sundstrom
1586
answered Jun 14 '18 at 21:40
Andrew SundstromAndrew Sundstrom
1586
answered Jun 14 '18 at 21:40
Andrew SundstromAndrew Sundstrom
1586
answered Jun 14 '18 at 21:40
Andrew SundstromAndrew Sundstrom
1586
1586
Then either you already have TL 2018 or you are still using an earlier edition. Note that the question concerned the pre-test and was posted in April .... Can you update using this command from pre-test to release?
– cfr
Jun 15 '18 at 3:20
@cfr Yes, I already had TexLive-2018 installed and ran into this bug. But I’m afraid I don’t know how to do what you suggest.
– Andrew Sundstrom
Jun 15 '18 at 3:26
add a comment |
Then either you already have TL 2018 or you are still using an earlier edition. Note that the question concerned the pre-test and was posted in April .... Can you update using this command from pre-test to release?
– cfr
Jun 15 '18 at 3:20
@cfr Yes, I already had TexLive-2018 installed and ran into this bug. But I’m afraid I don’t know how to do what you suggest.
– Andrew Sundstrom
Jun 15 '18 at 3:26
Then either you already have TL 2018 or you are still using an earlier edition. Note that the question concerned the pre-test and was posted in April .... Can you update using this command from pre-test to release?
– cfr
Jun 15 '18 at 3:20
Then either you already have TL 2018 or you are still using an earlier edition. Note that the question concerned the pre-test and was posted in April .... Can you update using this command from pre-test to release?
– cfr
Jun 15 '18 at 3:20
@cfr Yes, I already had TexLive-2018 installed and ran into this bug. But I’m afraid I don’t know how to do what you suggest.
– Andrew Sundstrom
Jun 15 '18 at 3:26
@cfr Yes, I already had TexLive-2018 installed and ran into this bug. But I’m afraid I don’t know how to do what you suggest.
– Andrew Sundstrom
Jun 15 '18 at 3:26
add a comment |
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f426088%2ftexlive-pretest-2018-beamer-and-subfig-collide%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
1
github.com/josephwright/beamer/issues
– Henri Menke
Apr 11 '18 at 23:51
1
I'm voting to close this question as off-topic because TeX.SX is not an issue tracker.
– Henri Menke
Apr 11 '18 at 23:51
@HenriMenke why beamer, the code is in caption?
– David Carlisle
Apr 11 '18 at 23:54
12
@HenriMenke IMO that's not a good reason to close, for a few reasons: (1) I It's hard in general for a user, encountering some trouble with getting their work done, to know whether something is a real issue to be reported, or just something they ought to do differently, (2) Even if it seems a bug, the “proper place” to report is often not clear: is hard to know which package/code has an issue, (3) Even if it's a bug that can be reported at an issue tracker, usually users just want to learn a workaround from TeX experts so that they can continue getting their work done. So it's on-topic IMO.
– ShreevatsaR
Apr 11 '18 at 23:57
7
@HenriMenke the code is not in beamer or in subfig, it is in caption3.sty. As explained in the accepted answer of the meta question you linked to if the question is not clearly just a bug report on a known package there is merit in asking the question and answering it here
– David Carlisle
Apr 12 '18 at 0:19