Is it bad to have ref before you have label and if so what to do about it?
Overleaf issues a lot of warnings about having ref before I have label and idk if I should do anything about it.
labels
asked Feb 8 at 15:35
Hao SunHao Sun
15518
add a comment |
Overleaf issues a lot of warnings about having ref before I have label and idk if I should do anything about it.
labels
asked Feb 8 at 15:35
Hao SunHao Sun
15518
6
There's no problem about that. In the second compilation pass LaTeX will sort things out and therefs will point to the correctlabels, wherever they are. What is the exact warning message that Overleaf shows?
– Phelype Oleinik
Feb 8 at 15:36
1
There should be no TeXnical reason against this and I have never seen a warning issued by (La)TeX about this. Can you show us a short code example that reproduces such a warning by Overleaf (a so-called MWE: tex.meta.stackexchange.com/q/228/35864) as well as the exact message Overleaf shows. It could be a stylistic issue, but academia.stackexchange.com/q/38236 suggests there is definitely no consensus that mentioning (refing) a float before it appears (label) is bad.
– moewe
Feb 8 at 16:00
add a comment |
Overleaf issues a lot of warnings about having ref before I have label and idk if I should do anything about it.
labels
asked Feb 8 at 15:35
Hao SunHao Sun
15518
Overleaf issues a lot of warnings about having ref before I have label and idk if I should do anything about it.
labels
labels
asked Feb 8 at 15:35
Hao SunHao Sun
15518
asked Feb 8 at 15:35
Hao SunHao Sun
15518
asked Feb 8 at 15:35
Hao SunHao Sun
15518
asked Feb 8 at 15:35
Hao SunHao Sun
15518
asked Feb 8 at 15:35
Hao SunHao Sun
15518
15518
6
There's no problem about that. In the second compilation pass LaTeX will sort things out and therefs will point to the correctlabels, wherever they are. What is the exact warning message that Overleaf shows?
– Phelype Oleinik
Feb 8 at 15:36
1
There should be no TeXnical reason against this and I have never seen a warning issued by (La)TeX about this. Can you show us a short code example that reproduces such a warning by Overleaf (a so-called MWE: tex.meta.stackexchange.com/q/228/35864) as well as the exact message Overleaf shows. It could be a stylistic issue, but academia.stackexchange.com/q/38236 suggests there is definitely no consensus that mentioning (refing) a float before it appears (label) is bad.
– moewe
Feb 8 at 16:00
add a comment |
6
There's no problem about that. In the second compilation pass LaTeX will sort things out and therefs will point to the correctlabels, wherever they are. What is the exact warning message that Overleaf shows?
– Phelype Oleinik
Feb 8 at 15:36
1
There should be no TeXnical reason against this and I have never seen a warning issued by (La)TeX about this. Can you show us a short code example that reproduces such a warning by Overleaf (a so-called MWE: tex.meta.stackexchange.com/q/228/35864) as well as the exact message Overleaf shows. It could be a stylistic issue, but academia.stackexchange.com/q/38236 suggests there is definitely no consensus that mentioning (refing) a float before it appears (label) is bad.
– moewe
Feb 8 at 16:00
6
6
There's no problem about that. In the second compilation pass LaTeX will sort things out and the
refs will point to the correct labels, wherever they are. What is the exact warning message that Overleaf shows?– Phelype Oleinik
Feb 8 at 15:36
There's no problem about that. In the second compilation pass LaTeX will sort things out and the
refs will point to the correct labels, wherever they are. What is the exact warning message that Overleaf shows?– Phelype Oleinik
Feb 8 at 15:36
1
1
There should be no TeXnical reason against this and I have never seen a warning issued by (La)TeX about this. Can you show us a short code example that reproduces such a warning by Overleaf (a so-called MWE: tex.meta.stackexchange.com/q/228/35864) as well as the exact message Overleaf shows. It could be a stylistic issue, but academia.stackexchange.com/q/38236 suggests there is definitely no consensus that mentioning (
refing) a float before it appears (label) is bad.– moewe
Feb 8 at 16:00
There should be no TeXnical reason against this and I have never seen a warning issued by (La)TeX about this. Can you show us a short code example that reproduces such a warning by Overleaf (a so-called MWE: tex.meta.stackexchange.com/q/228/35864) as well as the exact message Overleaf shows. It could be a stylistic issue, but academia.stackexchange.com/q/38236 suggests there is definitely no consensus that mentioning (
refing) a float before it appears (label) is bad.– moewe
Feb 8 at 16:00
add a comment |
1 Answer
1
active
oldest
votes
On the first compilation you will get warnings about undefined labels whether or not the label is before the ref. On later runs the cross references will resolve and the warnings will go.
This is assuming of course that there is not an error in the markup and the ref does refer to a valid label.
answered Feb 8 at 17:05
David CarlisleDavid Carlisle
490k4111341883
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%2f473944%2fis-it-bad-to-have-ref-before-you-have-label-and-if-so-what-to-do-about-it%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
On the first compilation you will get warnings about undefined labels whether or not the label is before the ref. On later runs the cross references will resolve and the warnings will go.
This is assuming of course that there is not an error in the markup and the ref does refer to a valid label.
answered Feb 8 at 17:05
David CarlisleDavid Carlisle
490k4111341883
add a comment |
On the first compilation you will get warnings about undefined labels whether or not the label is before the ref. On later runs the cross references will resolve and the warnings will go.
This is assuming of course that there is not an error in the markup and the ref does refer to a valid label.
answered Feb 8 at 17:05
David CarlisleDavid Carlisle
490k4111341883
add a comment |
On the first compilation you will get warnings about undefined labels whether or not the label is before the ref. On later runs the cross references will resolve and the warnings will go.
This is assuming of course that there is not an error in the markup and the ref does refer to a valid label.
answered Feb 8 at 17:05
David CarlisleDavid Carlisle
490k4111341883
On the first compilation you will get warnings about undefined labels whether or not the label is before the ref. On later runs the cross references will resolve and the warnings will go.
This is assuming of course that there is not an error in the markup and the ref does refer to a valid label.
answered Feb 8 at 17:05
David CarlisleDavid Carlisle
490k4111341883
answered Feb 8 at 17:05
David CarlisleDavid Carlisle
490k4111341883
answered Feb 8 at 17:05
David CarlisleDavid Carlisle
490k4111341883
answered Feb 8 at 17:05
David CarlisleDavid Carlisle
490k4111341883
490k4111341883
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%2f473944%2fis-it-bad-to-have-ref-before-you-have-label-and-if-so-what-to-do-about-it%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
6
There's no problem about that. In the second compilation pass LaTeX will sort things out and the
refs will point to the correctlabels, wherever they are. What is the exact warning message that Overleaf shows?– Phelype Oleinik
Feb 8 at 15:36
1
There should be no TeXnical reason against this and I have never seen a warning issued by (La)TeX about this. Can you show us a short code example that reproduces such a warning by Overleaf (a so-called MWE: tex.meta.stackexchange.com/q/228/35864) as well as the exact message Overleaf shows. It could be a stylistic issue, but academia.stackexchange.com/q/38236 suggests there is definitely no consensus that mentioning (
refing) a float before it appears (label) is bad.– moewe
Feb 8 at 16:00