List of figures showing id of figures not included
I tried to make two separate list of figures. One for Appendix I and one for Appendix E.
I found this code on stackexchange.com:
usepackage{titletoc}
startlist[main]{lof}% starts main list of figures
printlist[main]{lof}{}{}% prints main list of figures
begin{figure}
end{figure}
begin{figure}
end{figure}
clearpage
stoplist[main]{lof}% stops main list of figures
startlist[appendix]{lof}% starts list of figures in appendices
printlist[appendix]{lof}{}{}% prints list of figures in appendices
stoplist[appendix]{lof}
The problem is, that it shows the id of the figures, that are not included:
These figures are not supposed to be in this list.
How do I avoid this?
table-of-contents lists titletoc
asked Dec 20 '18 at 10:57
SofieSofie
1
add a comment |
I tried to make two separate list of figures. One for Appendix I and one for Appendix E.
I found this code on stackexchange.com:
usepackage{titletoc}
startlist[main]{lof}% starts main list of figures
printlist[main]{lof}{}{}% prints main list of figures
begin{figure}
end{figure}
begin{figure}
end{figure}
clearpage
stoplist[main]{lof}% stops main list of figures
startlist[appendix]{lof}% starts list of figures in appendices
printlist[appendix]{lof}{}{}% prints list of figures in appendices
stoplist[appendix]{lof}
The problem is, that it shows the id of the figures, that are not included:
These figures are not supposed to be in this list.
How do I avoid this?
table-of-contents lists titletoc
asked Dec 20 '18 at 10:57
SofieSofie
1
3
Please convert your code into a complete document including a document class - the so called minimal working example (MWE).
– epR8GaYuh
Dec 20 '18 at 10:58
2
@Sofie Hi and welcome to tex.se. Looks a bit as if you changed something with your packages recently. It's hard to guess withoutMWE, but did you try to delete all files*.aux,*.lof,*.lotand friends and rerun LaTeX?
– AndiW
Dec 20 '18 at 11:18
@epR8GaYuh I'll try to remember next time :) The code is relativly massive. When I tried to make a MWE it worked perfectly. So the mistake must be somewhere else in the code.
– Sofie
Dec 20 '18 at 11:32
@AndiW Thank you. Ill try it out!
– Sofie
Dec 20 '18 at 11:33
Note that it takes two or three runs to remove things from the aux file and lof file.
– John Kormylo
Dec 30 '18 at 16:49
add a comment |
I tried to make two separate list of figures. One for Appendix I and one for Appendix E.
I found this code on stackexchange.com:
usepackage{titletoc}
startlist[main]{lof}% starts main list of figures
printlist[main]{lof}{}{}% prints main list of figures
begin{figure}
end{figure}
begin{figure}
end{figure}
clearpage
stoplist[main]{lof}% stops main list of figures
startlist[appendix]{lof}% starts list of figures in appendices
printlist[appendix]{lof}{}{}% prints list of figures in appendices
stoplist[appendix]{lof}
The problem is, that it shows the id of the figures, that are not included:
These figures are not supposed to be in this list.
How do I avoid this?
table-of-contents lists titletoc
asked Dec 20 '18 at 10:57
SofieSofie
1
I tried to make two separate list of figures. One for Appendix I and one for Appendix E.
I found this code on stackexchange.com:
usepackage{titletoc}
startlist[main]{lof}% starts main list of figures
printlist[main]{lof}{}{}% prints main list of figures
begin{figure}
end{figure}
begin{figure}
end{figure}
clearpage
stoplist[main]{lof}% stops main list of figures
startlist[appendix]{lof}% starts list of figures in appendices
printlist[appendix]{lof}{}{}% prints list of figures in appendices
stoplist[appendix]{lof}
The problem is, that it shows the id of the figures, that are not included:
These figures are not supposed to be in this list.
How do I avoid this?
table-of-contents lists titletoc
table-of-contents lists titletoc
asked Dec 20 '18 at 10:57
SofieSofie
1
asked Dec 20 '18 at 10:57
SofieSofie
1
asked Dec 20 '18 at 10:57
SofieSofie
1
asked Dec 20 '18 at 10:57
SofieSofie
1
asked Dec 20 '18 at 10:57
SofieSofie
1
1
3
Please convert your code into a complete document including a document class - the so called minimal working example (MWE).
– epR8GaYuh
Dec 20 '18 at 10:58
2
@Sofie Hi and welcome to tex.se. Looks a bit as if you changed something with your packages recently. It's hard to guess withoutMWE, but did you try to delete all files*.aux,*.lof,*.lotand friends and rerun LaTeX?
– AndiW
Dec 20 '18 at 11:18
@epR8GaYuh I'll try to remember next time :) The code is relativly massive. When I tried to make a MWE it worked perfectly. So the mistake must be somewhere else in the code.
– Sofie
Dec 20 '18 at 11:32
@AndiW Thank you. Ill try it out!
– Sofie
Dec 20 '18 at 11:33
Note that it takes two or three runs to remove things from the aux file and lof file.
– John Kormylo
Dec 30 '18 at 16:49
add a comment |
3
Please convert your code into a complete document including a document class - the so called minimal working example (MWE).
– epR8GaYuh
Dec 20 '18 at 10:58
2
@Sofie Hi and welcome to tex.se. Looks a bit as if you changed something with your packages recently. It's hard to guess withoutMWE, but did you try to delete all files*.aux,*.lof,*.lotand friends and rerun LaTeX?
– AndiW
Dec 20 '18 at 11:18
@epR8GaYuh I'll try to remember next time :) The code is relativly massive. When I tried to make a MWE it worked perfectly. So the mistake must be somewhere else in the code.
– Sofie
Dec 20 '18 at 11:32
@AndiW Thank you. Ill try it out!
– Sofie
Dec 20 '18 at 11:33
Note that it takes two or three runs to remove things from the aux file and lof file.
– John Kormylo
Dec 30 '18 at 16:49
3
3
Please convert your code into a complete document including a document class - the so called minimal working example (MWE).
– epR8GaYuh
Dec 20 '18 at 10:58
Please convert your code into a complete document including a document class - the so called minimal working example (MWE).
– epR8GaYuh
Dec 20 '18 at 10:58
2
2
@Sofie Hi and welcome to tex.se. Looks a bit as if you changed something with your packages recently. It's hard to guess without
MWE, but did you try to delete all files *.aux, *.lof, *.lot and friends and rerun LaTeX?– AndiW
Dec 20 '18 at 11:18
@Sofie Hi and welcome to tex.se. Looks a bit as if you changed something with your packages recently. It's hard to guess without
MWE, but did you try to delete all files *.aux, *.lof, *.lot and friends and rerun LaTeX?– AndiW
Dec 20 '18 at 11:18
@epR8GaYuh I'll try to remember next time :) The code is relativly massive. When I tried to make a MWE it worked perfectly. So the mistake must be somewhere else in the code.
– Sofie
Dec 20 '18 at 11:32
@epR8GaYuh I'll try to remember next time :) The code is relativly massive. When I tried to make a MWE it worked perfectly. So the mistake must be somewhere else in the code.
– Sofie
Dec 20 '18 at 11:32
@AndiW Thank you. Ill try it out!
– Sofie
Dec 20 '18 at 11:33
@AndiW Thank you. Ill try it out!
– Sofie
Dec 20 '18 at 11:33
Note that it takes two or three runs to remove things from the aux file and lof file.
– John Kormylo
Dec 30 '18 at 16:49
Note that it takes two or three runs to remove things from the aux file and lof file.
– John Kormylo
Dec 30 '18 at 16:49
add a comment |
1 Answer
1
active
oldest
votes
Even if this might be not a real answer to the question I'd like to provide some basics about troubleshooting (La)TeX...
One of the most important things newbies (and we all have been newbies some day...) have to learn about (La)TeX is: it's a modular system. Some things are not known when (La)TeX is run for the first time: think about references, footnotes, bibliographies, anchors, internal links, ...
So the main technique (La)TeX uses is to export data to external files which can be loaded on subsequent runs of the compiler.
The basic external file is definitely the .aux-file(s) since it collects almost everything (La)TeX might need in advance. A non-actual .aux file is the reason you get messages like xyz changed. Rerun LaTeX to get them right.
But there are even more depending on what packages one uses: *.lot for table captions, *.lof for figure captions and others, depending on the packages one uses.
So the basic lection(s) I personally have learned in using LaTeX for over 30 years now is:
- Delete all auxiliary files. This includes folders other than the root folder in case you are using
include. - Update your (La)TeX distribiution whenever something seems to be odd.
- Remember what you have changed last. Creating regular backups of your TeX-files usually help a lot especially when you are working on a project of more than 5 pages.
- Use the same architecture (La)TeX uses. TeX and all of its derivates are modular, so
inputandincludeare your friends. Do not build monolytic blocks like in fx word (like coding 225+ macros in one file), place code snippets in subfiles to be able to track errors down once they occure. - This tip uses point 4: in case of trouble remove single (most of all the latest added) snippets by uncomment like
%input. - Try to minimize (also uses point 4): create a
test.texin the same root folder your project'smain.texis located and input only what's really needed to reproduce the error. This gives you the chance to spot cross-effects but also provides aMWEin case you have to ask on tex.se and friends. - Read the documentation. A good point to start is google with
CTAN <packagename>. Reading documentation is sometimes frustrating especially if it's short or extremely long - but search for hints of how things are coded and, even more important, of the idea behind it. - Use your most valuable friends
trace<what>andshow<what>. Placing things likeshow<macro>,showthe<counter or length>or general tracing of the things that happen (see this question for an excellent overview) usually helps a lot. - Do not hesitate to ask. We all have had our first day with (La)TeX, we all once have reached the point of maximal frustration (or even more than once), but we all have been going on because (La)TeX is the system that provides by far the most possibilities on the market (my opinion). No one on tex.se will ever forget those moments.
I am pretty sure that others using (La)TeX and tex.se are using other techniques to trace down errors. That's ok (LoL). The list above is certainly not complete - but in might provide a starting point to newbies and sometimes a reminder to pros...
answered Dec 20 '18 at 17:53
AndiWAndiW
250211
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%2f466670%2flist-of-figures-showing-id-of-figures-not-included%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
Even if this might be not a real answer to the question I'd like to provide some basics about troubleshooting (La)TeX...
One of the most important things newbies (and we all have been newbies some day...) have to learn about (La)TeX is: it's a modular system. Some things are not known when (La)TeX is run for the first time: think about references, footnotes, bibliographies, anchors, internal links, ...
So the main technique (La)TeX uses is to export data to external files which can be loaded on subsequent runs of the compiler.
The basic external file is definitely the .aux-file(s) since it collects almost everything (La)TeX might need in advance. A non-actual .aux file is the reason you get messages like xyz changed. Rerun LaTeX to get them right.
But there are even more depending on what packages one uses: *.lot for table captions, *.lof for figure captions and others, depending on the packages one uses.
So the basic lection(s) I personally have learned in using LaTeX for over 30 years now is:
- Delete all auxiliary files. This includes folders other than the root folder in case you are using
include. - Update your (La)TeX distribiution whenever something seems to be odd.
- Remember what you have changed last. Creating regular backups of your TeX-files usually help a lot especially when you are working on a project of more than 5 pages.
- Use the same architecture (La)TeX uses. TeX and all of its derivates are modular, so
inputandincludeare your friends. Do not build monolytic blocks like in fx word (like coding 225+ macros in one file), place code snippets in subfiles to be able to track errors down once they occure. - This tip uses point 4: in case of trouble remove single (most of all the latest added) snippets by uncomment like
%input. - Try to minimize (also uses point 4): create a
test.texin the same root folder your project'smain.texis located and input only what's really needed to reproduce the error. This gives you the chance to spot cross-effects but also provides aMWEin case you have to ask on tex.se and friends. - Read the documentation. A good point to start is google with
CTAN <packagename>. Reading documentation is sometimes frustrating especially if it's short or extremely long - but search for hints of how things are coded and, even more important, of the idea behind it. - Use your most valuable friends
trace<what>andshow<what>. Placing things likeshow<macro>,showthe<counter or length>or general tracing of the things that happen (see this question for an excellent overview) usually helps a lot. - Do not hesitate to ask. We all have had our first day with (La)TeX, we all once have reached the point of maximal frustration (or even more than once), but we all have been going on because (La)TeX is the system that provides by far the most possibilities on the market (my opinion). No one on tex.se will ever forget those moments.
I am pretty sure that others using (La)TeX and tex.se are using other techniques to trace down errors. That's ok (LoL). The list above is certainly not complete - but in might provide a starting point to newbies and sometimes a reminder to pros...
answered Dec 20 '18 at 17:53
AndiWAndiW
250211
add a comment |
Even if this might be not a real answer to the question I'd like to provide some basics about troubleshooting (La)TeX...
One of the most important things newbies (and we all have been newbies some day...) have to learn about (La)TeX is: it's a modular system. Some things are not known when (La)TeX is run for the first time: think about references, footnotes, bibliographies, anchors, internal links, ...
So the main technique (La)TeX uses is to export data to external files which can be loaded on subsequent runs of the compiler.
The basic external file is definitely the .aux-file(s) since it collects almost everything (La)TeX might need in advance. A non-actual .aux file is the reason you get messages like xyz changed. Rerun LaTeX to get them right.
But there are even more depending on what packages one uses: *.lot for table captions, *.lof for figure captions and others, depending on the packages one uses.
So the basic lection(s) I personally have learned in using LaTeX for over 30 years now is:
- Delete all auxiliary files. This includes folders other than the root folder in case you are using
include. - Update your (La)TeX distribiution whenever something seems to be odd.
- Remember what you have changed last. Creating regular backups of your TeX-files usually help a lot especially when you are working on a project of more than 5 pages.
- Use the same architecture (La)TeX uses. TeX and all of its derivates are modular, so
inputandincludeare your friends. Do not build monolytic blocks like in fx word (like coding 225+ macros in one file), place code snippets in subfiles to be able to track errors down once they occure. - This tip uses point 4: in case of trouble remove single (most of all the latest added) snippets by uncomment like
%input. - Try to minimize (also uses point 4): create a
test.texin the same root folder your project'smain.texis located and input only what's really needed to reproduce the error. This gives you the chance to spot cross-effects but also provides aMWEin case you have to ask on tex.se and friends. - Read the documentation. A good point to start is google with
CTAN <packagename>. Reading documentation is sometimes frustrating especially if it's short or extremely long - but search for hints of how things are coded and, even more important, of the idea behind it. - Use your most valuable friends
trace<what>andshow<what>. Placing things likeshow<macro>,showthe<counter or length>or general tracing of the things that happen (see this question for an excellent overview) usually helps a lot. - Do not hesitate to ask. We all have had our first day with (La)TeX, we all once have reached the point of maximal frustration (or even more than once), but we all have been going on because (La)TeX is the system that provides by far the most possibilities on the market (my opinion). No one on tex.se will ever forget those moments.
I am pretty sure that others using (La)TeX and tex.se are using other techniques to trace down errors. That's ok (LoL). The list above is certainly not complete - but in might provide a starting point to newbies and sometimes a reminder to pros...
answered Dec 20 '18 at 17:53
AndiWAndiW
250211
add a comment |
Even if this might be not a real answer to the question I'd like to provide some basics about troubleshooting (La)TeX...
One of the most important things newbies (and we all have been newbies some day...) have to learn about (La)TeX is: it's a modular system. Some things are not known when (La)TeX is run for the first time: think about references, footnotes, bibliographies, anchors, internal links, ...
So the main technique (La)TeX uses is to export data to external files which can be loaded on subsequent runs of the compiler.
The basic external file is definitely the .aux-file(s) since it collects almost everything (La)TeX might need in advance. A non-actual .aux file is the reason you get messages like xyz changed. Rerun LaTeX to get them right.
But there are even more depending on what packages one uses: *.lot for table captions, *.lof for figure captions and others, depending on the packages one uses.
So the basic lection(s) I personally have learned in using LaTeX for over 30 years now is:
- Delete all auxiliary files. This includes folders other than the root folder in case you are using
include. - Update your (La)TeX distribiution whenever something seems to be odd.
- Remember what you have changed last. Creating regular backups of your TeX-files usually help a lot especially when you are working on a project of more than 5 pages.
- Use the same architecture (La)TeX uses. TeX and all of its derivates are modular, so
inputandincludeare your friends. Do not build monolytic blocks like in fx word (like coding 225+ macros in one file), place code snippets in subfiles to be able to track errors down once they occure. - This tip uses point 4: in case of trouble remove single (most of all the latest added) snippets by uncomment like
%input. - Try to minimize (also uses point 4): create a
test.texin the same root folder your project'smain.texis located and input only what's really needed to reproduce the error. This gives you the chance to spot cross-effects but also provides aMWEin case you have to ask on tex.se and friends. - Read the documentation. A good point to start is google with
CTAN <packagename>. Reading documentation is sometimes frustrating especially if it's short or extremely long - but search for hints of how things are coded and, even more important, of the idea behind it. - Use your most valuable friends
trace<what>andshow<what>. Placing things likeshow<macro>,showthe<counter or length>or general tracing of the things that happen (see this question for an excellent overview) usually helps a lot. - Do not hesitate to ask. We all have had our first day with (La)TeX, we all once have reached the point of maximal frustration (or even more than once), but we all have been going on because (La)TeX is the system that provides by far the most possibilities on the market (my opinion). No one on tex.se will ever forget those moments.
I am pretty sure that others using (La)TeX and tex.se are using other techniques to trace down errors. That's ok (LoL). The list above is certainly not complete - but in might provide a starting point to newbies and sometimes a reminder to pros...
answered Dec 20 '18 at 17:53
AndiWAndiW
250211
Even if this might be not a real answer to the question I'd like to provide some basics about troubleshooting (La)TeX...
One of the most important things newbies (and we all have been newbies some day...) have to learn about (La)TeX is: it's a modular system. Some things are not known when (La)TeX is run for the first time: think about references, footnotes, bibliographies, anchors, internal links, ...
So the main technique (La)TeX uses is to export data to external files which can be loaded on subsequent runs of the compiler.
The basic external file is definitely the .aux-file(s) since it collects almost everything (La)TeX might need in advance. A non-actual .aux file is the reason you get messages like xyz changed. Rerun LaTeX to get them right.
But there are even more depending on what packages one uses: *.lot for table captions, *.lof for figure captions and others, depending on the packages one uses.
So the basic lection(s) I personally have learned in using LaTeX for over 30 years now is:
- Delete all auxiliary files. This includes folders other than the root folder in case you are using
include. - Update your (La)TeX distribiution whenever something seems to be odd.
- Remember what you have changed last. Creating regular backups of your TeX-files usually help a lot especially when you are working on a project of more than 5 pages.
- Use the same architecture (La)TeX uses. TeX and all of its derivates are modular, so
inputandincludeare your friends. Do not build monolytic blocks like in fx word (like coding 225+ macros in one file), place code snippets in subfiles to be able to track errors down once they occure. - This tip uses point 4: in case of trouble remove single (most of all the latest added) snippets by uncomment like
%input. - Try to minimize (also uses point 4): create a
test.texin the same root folder your project'smain.texis located and input only what's really needed to reproduce the error. This gives you the chance to spot cross-effects but also provides aMWEin case you have to ask on tex.se and friends. - Read the documentation. A good point to start is google with
CTAN <packagename>. Reading documentation is sometimes frustrating especially if it's short or extremely long - but search for hints of how things are coded and, even more important, of the idea behind it. - Use your most valuable friends
trace<what>andshow<what>. Placing things likeshow<macro>,showthe<counter or length>or general tracing of the things that happen (see this question for an excellent overview) usually helps a lot. - Do not hesitate to ask. We all have had our first day with (La)TeX, we all once have reached the point of maximal frustration (or even more than once), but we all have been going on because (La)TeX is the system that provides by far the most possibilities on the market (my opinion). No one on tex.se will ever forget those moments.
I am pretty sure that others using (La)TeX and tex.se are using other techniques to trace down errors. That's ok (LoL). The list above is certainly not complete - but in might provide a starting point to newbies and sometimes a reminder to pros...
answered Dec 20 '18 at 17:53
AndiWAndiW
250211
edited Dec 20 '18 at 20:26
answered Dec 20 '18 at 17:53
AndiWAndiW
250211
answered Dec 20 '18 at 17:53
AndiWAndiW
250211
answered Dec 20 '18 at 17:53
AndiWAndiW
250211
250211
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%2f466670%2flist-of-figures-showing-id-of-figures-not-included%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
3
Please convert your code into a complete document including a document class - the so called minimal working example (MWE).
– epR8GaYuh
Dec 20 '18 at 10:58
2
@Sofie Hi and welcome to tex.se. Looks a bit as if you changed something with your packages recently. It's hard to guess without
MWE, but did you try to delete all files*.aux,*.lof,*.lotand friends and rerun LaTeX?– AndiW
Dec 20 '18 at 11:18
@epR8GaYuh I'll try to remember next time :) The code is relativly massive. When I tried to make a MWE it worked perfectly. So the mistake must be somewhere else in the code.
– Sofie
Dec 20 '18 at 11:32
@AndiW Thank you. Ill try it out!
– Sofie
Dec 20 '18 at 11:33
Note that it takes two or three runs to remove things from the aux file and lof file.
– John Kormylo
Dec 30 '18 at 16:49