Extra space at the end of the document added by PGF
As seen in this answer to my previous question “Extra vertical space at end of last column when loading adjustbox (only luatex)”, loading the package pgf
causes the following to be added at the end of the document (in pgfutil-latex.def
):
AtBeginDocument{AtEndDocument{parvfilpenalty-10000relaxthepgfutil@everybye}}
As shown in the linked question, this can sometimes cause problems.
- Why is
pgf
doing this? - If I don’t know whether
pgf
will be loaded in a given document, how can I get rid of this space? (Without having to modify the document content)
spacing pgf-core hooks
add a comment |
As seen in this answer to my previous question “Extra vertical space at end of last column when loading adjustbox (only luatex)”, loading the package pgf
causes the following to be added at the end of the document (in pgfutil-latex.def
):
AtBeginDocument{AtEndDocument{parvfilpenalty-10000relaxthepgfutil@everybye}}
As shown in the linked question, this can sometimes cause problems.
- Why is
pgf
doing this? - If I don’t know whether
pgf
will be loaded in a given document, how can I get rid of this space? (Without having to modify the document content)
spacing pgf-core hooks
add a comment |
As seen in this answer to my previous question “Extra vertical space at end of last column when loading adjustbox (only luatex)”, loading the package pgf
causes the following to be added at the end of the document (in pgfutil-latex.def
):
AtBeginDocument{AtEndDocument{parvfilpenalty-10000relaxthepgfutil@everybye}}
As shown in the linked question, this can sometimes cause problems.
- Why is
pgf
doing this? - If I don’t know whether
pgf
will be loaded in a given document, how can I get rid of this space? (Without having to modify the document content)
spacing pgf-core hooks
As seen in this answer to my previous question “Extra vertical space at end of last column when loading adjustbox (only luatex)”, loading the package pgf
causes the following to be added at the end of the document (in pgfutil-latex.def
):
AtBeginDocument{AtEndDocument{parvfilpenalty-10000relaxthepgfutil@everybye}}
As shown in the linked question, this can sometimes cause problems.
- Why is
pgf
doing this? - If I don’t know whether
pgf
will be loaded in a given document, how can I get rid of this space? (Without having to modify the document content)
spacing pgf-core hooks
spacing pgf-core hooks
asked Oct 10 '18 at 0:46
SocobSocob
713516
713516
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
As to why pgf
is "doing this", it looks like a bug.
To deal with the faulty insertion of vertical space, you can try the following code just before begin{document}
makeatletter
ifdefinedpgfutil@everybye AtEndDocument{clearpagethepgfutil@everybye}elserelaxfi
makeatother
The answer to defining a fading-style directly in the fill command is informative, and I borrowed the AtEndDocument{...}
command from there.
How does this address what Ulrike wrote in the linked question? “In your example a work around is to add anewpage
beforeend{document}
. But ifpgf
puts something in the toks registerpgfutil@everybye
this could lead to a second page.” Also, wouldn’t this output whatever is inpgfutil@everybye
twice?
– Socob
Nov 10 '18 at 3:02
I wasn't really trying to address what Ulrike wrote in the linked question. I was suggesting that you use the code above in the preamble so you don't need to modify the body of the document. The code above more or less checks whether pgf is loaded. I tested the above code with your document and it seems to prevent the unwanted space being inserted. I have looked into the meaning ofpgfutil@everybye
and I think it's a bit beyond my understanding. I did wonder whether theAtEndDocument{...}
command could be "beaten" by anAtVeryEnd
or something similar. Have you tested the code above?
– corporal
Nov 11 '18 at 5:54
add a comment |
As revealed in a comment by Henri Menke, it seems that this issue should be addressed in a future PGF release:
https://sourceforge.net/u/hmenke/pgf/ci/fbfabbd01cecb4e8b6b1e43d1f3ad685c7e60778/
I had also opened a bug report on the PGF/TikZ tracker: #502 PGF can cause extra space at the end of a document (pgfutil@everybye).
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
});
}
});
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%2f454581%2fextra-space-at-the-end-of-the-document-added-by-pgf%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
As to why pgf
is "doing this", it looks like a bug.
To deal with the faulty insertion of vertical space, you can try the following code just before begin{document}
makeatletter
ifdefinedpgfutil@everybye AtEndDocument{clearpagethepgfutil@everybye}elserelaxfi
makeatother
The answer to defining a fading-style directly in the fill command is informative, and I borrowed the AtEndDocument{...}
command from there.
How does this address what Ulrike wrote in the linked question? “In your example a work around is to add anewpage
beforeend{document}
. But ifpgf
puts something in the toks registerpgfutil@everybye
this could lead to a second page.” Also, wouldn’t this output whatever is inpgfutil@everybye
twice?
– Socob
Nov 10 '18 at 3:02
I wasn't really trying to address what Ulrike wrote in the linked question. I was suggesting that you use the code above in the preamble so you don't need to modify the body of the document. The code above more or less checks whether pgf is loaded. I tested the above code with your document and it seems to prevent the unwanted space being inserted. I have looked into the meaning ofpgfutil@everybye
and I think it's a bit beyond my understanding. I did wonder whether theAtEndDocument{...}
command could be "beaten" by anAtVeryEnd
or something similar. Have you tested the code above?
– corporal
Nov 11 '18 at 5:54
add a comment |
As to why pgf
is "doing this", it looks like a bug.
To deal with the faulty insertion of vertical space, you can try the following code just before begin{document}
makeatletter
ifdefinedpgfutil@everybye AtEndDocument{clearpagethepgfutil@everybye}elserelaxfi
makeatother
The answer to defining a fading-style directly in the fill command is informative, and I borrowed the AtEndDocument{...}
command from there.
How does this address what Ulrike wrote in the linked question? “In your example a work around is to add anewpage
beforeend{document}
. But ifpgf
puts something in the toks registerpgfutil@everybye
this could lead to a second page.” Also, wouldn’t this output whatever is inpgfutil@everybye
twice?
– Socob
Nov 10 '18 at 3:02
I wasn't really trying to address what Ulrike wrote in the linked question. I was suggesting that you use the code above in the preamble so you don't need to modify the body of the document. The code above more or less checks whether pgf is loaded. I tested the above code with your document and it seems to prevent the unwanted space being inserted. I have looked into the meaning ofpgfutil@everybye
and I think it's a bit beyond my understanding. I did wonder whether theAtEndDocument{...}
command could be "beaten" by anAtVeryEnd
or something similar. Have you tested the code above?
– corporal
Nov 11 '18 at 5:54
add a comment |
As to why pgf
is "doing this", it looks like a bug.
To deal with the faulty insertion of vertical space, you can try the following code just before begin{document}
makeatletter
ifdefinedpgfutil@everybye AtEndDocument{clearpagethepgfutil@everybye}elserelaxfi
makeatother
The answer to defining a fading-style directly in the fill command is informative, and I borrowed the AtEndDocument{...}
command from there.
As to why pgf
is "doing this", it looks like a bug.
To deal with the faulty insertion of vertical space, you can try the following code just before begin{document}
makeatletter
ifdefinedpgfutil@everybye AtEndDocument{clearpagethepgfutil@everybye}elserelaxfi
makeatother
The answer to defining a fading-style directly in the fill command is informative, and I borrowed the AtEndDocument{...}
command from there.
answered Nov 8 '18 at 3:21
corporalcorporal
68146
68146
How does this address what Ulrike wrote in the linked question? “In your example a work around is to add anewpage
beforeend{document}
. But ifpgf
puts something in the toks registerpgfutil@everybye
this could lead to a second page.” Also, wouldn’t this output whatever is inpgfutil@everybye
twice?
– Socob
Nov 10 '18 at 3:02
I wasn't really trying to address what Ulrike wrote in the linked question. I was suggesting that you use the code above in the preamble so you don't need to modify the body of the document. The code above more or less checks whether pgf is loaded. I tested the above code with your document and it seems to prevent the unwanted space being inserted. I have looked into the meaning ofpgfutil@everybye
and I think it's a bit beyond my understanding. I did wonder whether theAtEndDocument{...}
command could be "beaten" by anAtVeryEnd
or something similar. Have you tested the code above?
– corporal
Nov 11 '18 at 5:54
add a comment |
How does this address what Ulrike wrote in the linked question? “In your example a work around is to add anewpage
beforeend{document}
. But ifpgf
puts something in the toks registerpgfutil@everybye
this could lead to a second page.” Also, wouldn’t this output whatever is inpgfutil@everybye
twice?
– Socob
Nov 10 '18 at 3:02
I wasn't really trying to address what Ulrike wrote in the linked question. I was suggesting that you use the code above in the preamble so you don't need to modify the body of the document. The code above more or less checks whether pgf is loaded. I tested the above code with your document and it seems to prevent the unwanted space being inserted. I have looked into the meaning ofpgfutil@everybye
and I think it's a bit beyond my understanding. I did wonder whether theAtEndDocument{...}
command could be "beaten" by anAtVeryEnd
or something similar. Have you tested the code above?
– corporal
Nov 11 '18 at 5:54
How does this address what Ulrike wrote in the linked question? “In your example a work around is to add a
newpage
before end{document}
. But if pgf
puts something in the toks register pgfutil@everybye
this could lead to a second page.” Also, wouldn’t this output whatever is in pgfutil@everybye
twice?– Socob
Nov 10 '18 at 3:02
How does this address what Ulrike wrote in the linked question? “In your example a work around is to add a
newpage
before end{document}
. But if pgf
puts something in the toks register pgfutil@everybye
this could lead to a second page.” Also, wouldn’t this output whatever is in pgfutil@everybye
twice?– Socob
Nov 10 '18 at 3:02
I wasn't really trying to address what Ulrike wrote in the linked question. I was suggesting that you use the code above in the preamble so you don't need to modify the body of the document. The code above more or less checks whether pgf is loaded. I tested the above code with your document and it seems to prevent the unwanted space being inserted. I have looked into the meaning of
pgfutil@everybye
and I think it's a bit beyond my understanding. I did wonder whether the AtEndDocument{...}
command could be "beaten" by an AtVeryEnd
or something similar. Have you tested the code above?– corporal
Nov 11 '18 at 5:54
I wasn't really trying to address what Ulrike wrote in the linked question. I was suggesting that you use the code above in the preamble so you don't need to modify the body of the document. The code above more or less checks whether pgf is loaded. I tested the above code with your document and it seems to prevent the unwanted space being inserted. I have looked into the meaning of
pgfutil@everybye
and I think it's a bit beyond my understanding. I did wonder whether the AtEndDocument{...}
command could be "beaten" by an AtVeryEnd
or something similar. Have you tested the code above?– corporal
Nov 11 '18 at 5:54
add a comment |
As revealed in a comment by Henri Menke, it seems that this issue should be addressed in a future PGF release:
https://sourceforge.net/u/hmenke/pgf/ci/fbfabbd01cecb4e8b6b1e43d1f3ad685c7e60778/
I had also opened a bug report on the PGF/TikZ tracker: #502 PGF can cause extra space at the end of a document (pgfutil@everybye).
add a comment |
As revealed in a comment by Henri Menke, it seems that this issue should be addressed in a future PGF release:
https://sourceforge.net/u/hmenke/pgf/ci/fbfabbd01cecb4e8b6b1e43d1f3ad685c7e60778/
I had also opened a bug report on the PGF/TikZ tracker: #502 PGF can cause extra space at the end of a document (pgfutil@everybye).
add a comment |
As revealed in a comment by Henri Menke, it seems that this issue should be addressed in a future PGF release:
https://sourceforge.net/u/hmenke/pgf/ci/fbfabbd01cecb4e8b6b1e43d1f3ad685c7e60778/
I had also opened a bug report on the PGF/TikZ tracker: #502 PGF can cause extra space at the end of a document (pgfutil@everybye).
As revealed in a comment by Henri Menke, it seems that this issue should be addressed in a future PGF release:
https://sourceforge.net/u/hmenke/pgf/ci/fbfabbd01cecb4e8b6b1e43d1f3ad685c7e60778/
I had also opened a bug report on the PGF/TikZ tracker: #502 PGF can cause extra space at the end of a document (pgfutil@everybye).
answered 18 mins ago
SocobSocob
713516
713516
add a comment |
add a comment |
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%2f454581%2fextra-space-at-the-end-of-the-document-added-by-pgf%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