Mixing
General question: How do understand latex warnings and errors? Is there any documentation on it?
Lots of times I get warnings or errors, but I can never figure out how to decipher them and I can't find any good documentation or guide going through how to understand these errors. For example: 
I am using latexmk -pdf -pvc. For this, where does the section talking about the errors in Chapter 2. begin? Is it exactly where it says Chapter 2.? Also What is all the other stuff before that talking about? Like the usr/local/texlive/2018... What does it mean T1/cmr/m/n/12 (+20) in the error for Overfull hbox? In general how do I go about reading these?
Also, just as a side question, I can't figure out how to fix those hbox errors. I used to use sloppywhich fixed some errors but those errors aren't being solved using that. I have also tried using usepackage{microtype} which did not fix the problem either.
formatting pdftex
asked Jan 4 at 23:22
appljuiceappljuice
182
|
show 1 more comment
Lots of times I get warnings or errors, but I can never figure out how to decipher them and I can't find any good documentation or guide going through how to understand these errors. For example:
I am using latexmk -pdf -pvc. For this, where does the section talking about the errors in Chapter 2. begin? Is it exactly where it says Chapter 2.? Also What is all the other stuff before that talking about? Like the usr/local/texlive/2018... What does it mean T1/cmr/m/n/12 (+20) in the error for Overfull hbox? In general how do I go about reading these?
Also, just as a side question, I can't figure out how to fix those hbox errors. I used to use sloppywhich fixed some errors but those errors aren't being solved using that. I have also tried using usepackage{microtype} which did not fix the problem either.
formatting pdftex
asked Jan 4 at 23:22
appljuiceappljuice
182
2
Welcome to TeX.SE! I can only see warnings, no errors. (Generally you should not use screen shots for code or text output.) These things happen if LaTeX "thinks" that the line breaks have room for improvements. Depending on what you are doing (you do not provide the source code) providing the hyphenation of certain word in that line may already make this warning disappear. If you want more information, please provide a minimal working example that produces these warnings.
– marmot
Jan 4 at 23:23
1
Yes, we can google code that we can copy more quickly than code that we have to punch in. ;-) More seriously, you see that there are links on the right-hand side. They are generated based on the contents. If your contents contained "overfull", you would see more helpful links even when typing your question.
– marmot
Jan 4 at 23:29
1
Some people are not fortunate enough to be able to read the text in the picture, but they may well have software that can read text to them. It is also more convenient for people who can see the text in the picture when they can copy and paste parts of your error messages to explain them to you. Finally, web searches can pick up text, but are not (yet) great at picking up text from pictures.
– moewe
Jan 4 at 23:29
1
The LaTeX Companion has at the end a good overview over many error messages.
– Ulrike Fischer
Jan 4 at 23:30
1
When I did a quick google search withsite:tex.stackexchange.com overfull, I got dragged here, which IMHO provides some good information on parts of your question. In my experience, google searches withsite:tex.stackexchange.comin tend to be more efficient than searches with the tool provided by this site (unfortunately).
– marmot
Jan 4 at 23:33
|
show 1 more comment
Lots of times I get warnings or errors, but I can never figure out how to decipher them and I can't find any good documentation or guide going through how to understand these errors. For example:
I am using latexmk -pdf -pvc. For this, where does the section talking about the errors in Chapter 2. begin? Is it exactly where it says Chapter 2.? Also What is all the other stuff before that talking about? Like the usr/local/texlive/2018... What does it mean T1/cmr/m/n/12 (+20) in the error for Overfull hbox? In general how do I go about reading these?
Also, just as a side question, I can't figure out how to fix those hbox errors. I used to use sloppywhich fixed some errors but those errors aren't being solved using that. I have also tried using usepackage{microtype} which did not fix the problem either.
formatting pdftex
asked Jan 4 at 23:22
appljuiceappljuice
182
Lots of times I get warnings or errors, but I can never figure out how to decipher them and I can't find any good documentation or guide going through how to understand these errors. For example:
I am using latexmk -pdf -pvc. For this, where does the section talking about the errors in Chapter 2. begin? Is it exactly where it says Chapter 2.? Also What is all the other stuff before that talking about? Like the usr/local/texlive/2018... What does it mean T1/cmr/m/n/12 (+20) in the error for Overfull hbox? In general how do I go about reading these?
Also, just as a side question, I can't figure out how to fix those hbox errors. I used to use sloppywhich fixed some errors but those errors aren't being solved using that. I have also tried using usepackage{microtype} which did not fix the problem either.
formatting pdftex
formatting pdftex
asked Jan 4 at 23:22
appljuiceappljuice
182
asked Jan 4 at 23:22
appljuiceappljuice
182
asked Jan 4 at 23:22
appljuiceappljuice
182
asked Jan 4 at 23:22
appljuiceappljuice
182
asked Jan 4 at 23:22
appljuiceappljuice
182
182
2
Welcome to TeX.SE! I can only see warnings, no errors. (Generally you should not use screen shots for code or text output.) These things happen if LaTeX "thinks" that the line breaks have room for improvements. Depending on what you are doing (you do not provide the source code) providing the hyphenation of certain word in that line may already make this warning disappear. If you want more information, please provide a minimal working example that produces these warnings.
– marmot
Jan 4 at 23:23
1
Yes, we can google code that we can copy more quickly than code that we have to punch in. ;-) More seriously, you see that there are links on the right-hand side. They are generated based on the contents. If your contents contained "overfull", you would see more helpful links even when typing your question.
– marmot
Jan 4 at 23:29
1
Some people are not fortunate enough to be able to read the text in the picture, but they may well have software that can read text to them. It is also more convenient for people who can see the text in the picture when they can copy and paste parts of your error messages to explain them to you. Finally, web searches can pick up text, but are not (yet) great at picking up text from pictures.
– moewe
Jan 4 at 23:29
1
The LaTeX Companion has at the end a good overview over many error messages.
– Ulrike Fischer
Jan 4 at 23:30
1
When I did a quick google search withsite:tex.stackexchange.com overfull, I got dragged here, which IMHO provides some good information on parts of your question. In my experience, google searches withsite:tex.stackexchange.comin tend to be more efficient than searches with the tool provided by this site (unfortunately).
– marmot
Jan 4 at 23:33
|
show 1 more comment
2
Welcome to TeX.SE! I can only see warnings, no errors. (Generally you should not use screen shots for code or text output.) These things happen if LaTeX "thinks" that the line breaks have room for improvements. Depending on what you are doing (you do not provide the source code) providing the hyphenation of certain word in that line may already make this warning disappear. If you want more information, please provide a minimal working example that produces these warnings.
– marmot
Jan 4 at 23:23
1
Yes, we can google code that we can copy more quickly than code that we have to punch in. ;-) More seriously, you see that there are links on the right-hand side. They are generated based on the contents. If your contents contained "overfull", you would see more helpful links even when typing your question.
– marmot
Jan 4 at 23:29
1
Some people are not fortunate enough to be able to read the text in the picture, but they may well have software that can read text to them. It is also more convenient for people who can see the text in the picture when they can copy and paste parts of your error messages to explain them to you. Finally, web searches can pick up text, but are not (yet) great at picking up text from pictures.
– moewe
Jan 4 at 23:29
1
The LaTeX Companion has at the end a good overview over many error messages.
– Ulrike Fischer
Jan 4 at 23:30
1
When I did a quick google search withsite:tex.stackexchange.com overfull, I got dragged here, which IMHO provides some good information on parts of your question. In my experience, google searches withsite:tex.stackexchange.comin tend to be more efficient than searches with the tool provided by this site (unfortunately).
– marmot
Jan 4 at 23:33
2
2
Welcome to TeX.SE! I can only see warnings, no errors. (Generally you should not use screen shots for code or text output.) These things happen if LaTeX "thinks" that the line breaks have room for improvements. Depending on what you are doing (you do not provide the source code) providing the hyphenation of certain word in that line may already make this warning disappear. If you want more information, please provide a minimal working example that produces these warnings.
– marmot
Jan 4 at 23:23
Welcome to TeX.SE! I can only see warnings, no errors. (Generally you should not use screen shots for code or text output.) These things happen if LaTeX "thinks" that the line breaks have room for improvements. Depending on what you are doing (you do not provide the source code) providing the hyphenation of certain word in that line may already make this warning disappear. If you want more information, please provide a minimal working example that produces these warnings.
– marmot
Jan 4 at 23:23
1
1
Yes, we can google code that we can copy more quickly than code that we have to punch in. ;-) More seriously, you see that there are links on the right-hand side. They are generated based on the contents. If your contents contained "overfull", you would see more helpful links even when typing your question.
– marmot
Jan 4 at 23:29
Yes, we can google code that we can copy more quickly than code that we have to punch in. ;-) More seriously, you see that there are links on the right-hand side. They are generated based on the contents. If your contents contained "overfull", you would see more helpful links even when typing your question.
– marmot
Jan 4 at 23:29
1
1
Some people are not fortunate enough to be able to read the text in the picture, but they may well have software that can read text to them. It is also more convenient for people who can see the text in the picture when they can copy and paste parts of your error messages to explain them to you. Finally, web searches can pick up text, but are not (yet) great at picking up text from pictures.
– moewe
Jan 4 at 23:29
Some people are not fortunate enough to be able to read the text in the picture, but they may well have software that can read text to them. It is also more convenient for people who can see the text in the picture when they can copy and paste parts of your error messages to explain them to you. Finally, web searches can pick up text, but are not (yet) great at picking up text from pictures.
– moewe
Jan 4 at 23:29
1
1
The LaTeX Companion has at the end a good overview over many error messages.
– Ulrike Fischer
Jan 4 at 23:30
The LaTeX Companion has at the end a good overview over many error messages.
– Ulrike Fischer
Jan 4 at 23:30
1
1
When I did a quick google search with
site:tex.stackexchange.com overfull, I got dragged here, which IMHO provides some good information on parts of your question. In my experience, google searches with site:tex.stackexchange.com in tend to be more efficient than searches with the tool provided by this site (unfortunately).– marmot
Jan 4 at 23:33
When I did a quick google search with
site:tex.stackexchange.com overfull, I got dragged here, which IMHO provides some good information on parts of your question. In my experience, google searches with site:tex.stackexchange.com in tend to be more efficient than searches with the tool provided by this site (unfortunately).– marmot
Jan 4 at 23:33
|
show 1 more comment
1 Answer
1
active
oldest
votes
The comments have pointed you at existing answers describing the general issue but I'll try to describe the log output you show (it would have been a lot easier if you had posted that as text not an image) but I OCR'd the image here:
(/usr/local/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
) (/usr/local/texlive/2018/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
(/usr/local/texlive/2018/texmf-dist/tex/latex/oberdiek/grfext.sty)
(/usr/local/texlive/2018/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
ABD: EverySelectfont initializing macros ABD: EveryShipout initializing macros
(/usr/local/texlive/2018/texmf-dist/tex/latex/microtype/mt-cmr.cfg) [1{/usr/loc
al/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]
(~/CS188Notes.tex
Chapter 2.
Overfull hbox (0.12741pt too wide) in paragraph at lines 27--29
T1/cmr/m/n/12 (+20) brains are good at making rational. But the main problem i
s that brains are not modular
[7] [8] Chapter 3.
The first thing to note is that TeX wraps the messages at a (user settable) width
and then whenever it input a file it logs ( followed by the file path, and when it finishes with that file and processing returns to the file that processed the input Tex logs ).
The graphics package internally does input{supp-pdf.mkii} which on your system gets logged as
(/usr/local/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
as that is the directory where the file was located. that file identifies itself with a message so then you see
[Loading MPS to PDF converter (version 2006.09.02).]
and a newline then that file is finished so you see ) At this point graphics inputs epstopdf-base.sty which in turn inputs grfext.sty and epstopdf-sys.cfg then you see )) as both levels of input have finished. Then some package outputs two identifying messages prefixed with ABD: then a microtype cfg file is input
(/usr/local/texlive/2018/texmf-dist/tex/latex/microtype/mt-cmr.cfg)
at this point TeX has finished typesetting page 1 and starts to output that page so you see [1 in the log, while generating the PDF for that page it needs to access some font data so you see (wrapped)
{/usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}
where {...} is a pdftex logging of an internal input as oppsed to the classic (...0 logging of an explicit input.
then you see ] denoting page 1 being finally shipped out.
TeX now presumably sees an input of your CS188Notes file and logs
(~/CS188Notes.tex
The chapter` command in there logs:
Chapter 2.
so up to this point everything is good, the messages are just informational.
Now we see
Overfull hbox (0.12741pt too wide) in paragraph at lines 27--29
So something is .1pt (not very much:-) too wide on the page after page 1 and on line 27 of the source file ~/CS188Notes.tex Te actual text is logged as
T1/cmr/m/n/12 (+20) brains are good at making rational. But the main problem i
s that brains are not modular
so it is that sentence, set in T1 (Latin) encoded computer modern medium weight, normal shape 12pt font, adjusted (+20) by microtype.
then somewhat strangely TeX logs
[7][8]
which means pages 7 and 8 got output (did you increment the page counter, what happened to pages 2 to 6 ?
Then another chapter command logs
chapter 3
So the only thing wrong is the text about brains where tex couldn't find an ideal line break, it's only .1pt so you could ignore it (if you set hfuzz to .2pt then TeX would not warn about this at all or you may want to adjust the typesetting (or wording) of that paragraph to help with line breaking.
answered Jan 5 at 0:09
David CarlisleDavid Carlisle
486k4111221867
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%2f468662%2fgeneral-question-how-do-understand-latex-warnings-and-errors-is-there-any-docu%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
The comments have pointed you at existing answers describing the general issue but I'll try to describe the log output you show (it would have been a lot easier if you had posted that as text not an image) but I OCR'd the image here:
(/usr/local/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
) (/usr/local/texlive/2018/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
(/usr/local/texlive/2018/texmf-dist/tex/latex/oberdiek/grfext.sty)
(/usr/local/texlive/2018/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
ABD: EverySelectfont initializing macros ABD: EveryShipout initializing macros
(/usr/local/texlive/2018/texmf-dist/tex/latex/microtype/mt-cmr.cfg) [1{/usr/loc
al/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]
(~/CS188Notes.tex
Chapter 2.
Overfull hbox (0.12741pt too wide) in paragraph at lines 27--29
T1/cmr/m/n/12 (+20) brains are good at making rational. But the main problem i
s that brains are not modular
[7] [8] Chapter 3.
The first thing to note is that TeX wraps the messages at a (user settable) width
and then whenever it input a file it logs ( followed by the file path, and when it finishes with that file and processing returns to the file that processed the input Tex logs ).
The graphics package internally does input{supp-pdf.mkii} which on your system gets logged as
(/usr/local/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
as that is the directory where the file was located. that file identifies itself with a message so then you see
[Loading MPS to PDF converter (version 2006.09.02).]
and a newline then that file is finished so you see ) At this point graphics inputs epstopdf-base.sty which in turn inputs grfext.sty and epstopdf-sys.cfg then you see )) as both levels of input have finished. Then some package outputs two identifying messages prefixed with ABD: then a microtype cfg file is input
(/usr/local/texlive/2018/texmf-dist/tex/latex/microtype/mt-cmr.cfg)
at this point TeX has finished typesetting page 1 and starts to output that page so you see [1 in the log, while generating the PDF for that page it needs to access some font data so you see (wrapped)
{/usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}
where {...} is a pdftex logging of an internal input as oppsed to the classic (...0 logging of an explicit input.
then you see ] denoting page 1 being finally shipped out.
TeX now presumably sees an input of your CS188Notes file and logs
(~/CS188Notes.tex
The chapter` command in there logs:
Chapter 2.
so up to this point everything is good, the messages are just informational.
Now we see
Overfull hbox (0.12741pt too wide) in paragraph at lines 27--29
So something is .1pt (not very much:-) too wide on the page after page 1 and on line 27 of the source file ~/CS188Notes.tex Te actual text is logged as
T1/cmr/m/n/12 (+20) brains are good at making rational. But the main problem i
s that brains are not modular
so it is that sentence, set in T1 (Latin) encoded computer modern medium weight, normal shape 12pt font, adjusted (+20) by microtype.
then somewhat strangely TeX logs
[7][8]
which means pages 7 and 8 got output (did you increment the page counter, what happened to pages 2 to 6 ?
Then another chapter command logs
chapter 3
So the only thing wrong is the text about brains where tex couldn't find an ideal line break, it's only .1pt so you could ignore it (if you set hfuzz to .2pt then TeX would not warn about this at all or you may want to adjust the typesetting (or wording) of that paragraph to help with line breaking.
answered Jan 5 at 0:09
David CarlisleDavid Carlisle
486k4111221867
add a comment |
The comments have pointed you at existing answers describing the general issue but I'll try to describe the log output you show (it would have been a lot easier if you had posted that as text not an image) but I OCR'd the image here:
(/usr/local/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
) (/usr/local/texlive/2018/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
(/usr/local/texlive/2018/texmf-dist/tex/latex/oberdiek/grfext.sty)
(/usr/local/texlive/2018/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
ABD: EverySelectfont initializing macros ABD: EveryShipout initializing macros
(/usr/local/texlive/2018/texmf-dist/tex/latex/microtype/mt-cmr.cfg) [1{/usr/loc
al/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]
(~/CS188Notes.tex
Chapter 2.
Overfull hbox (0.12741pt too wide) in paragraph at lines 27--29
T1/cmr/m/n/12 (+20) brains are good at making rational. But the main problem i
s that brains are not modular
[7] [8] Chapter 3.
The first thing to note is that TeX wraps the messages at a (user settable) width
and then whenever it input a file it logs ( followed by the file path, and when it finishes with that file and processing returns to the file that processed the input Tex logs ).
The graphics package internally does input{supp-pdf.mkii} which on your system gets logged as
(/usr/local/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
as that is the directory where the file was located. that file identifies itself with a message so then you see
[Loading MPS to PDF converter (version 2006.09.02).]
and a newline then that file is finished so you see ) At this point graphics inputs epstopdf-base.sty which in turn inputs grfext.sty and epstopdf-sys.cfg then you see )) as both levels of input have finished. Then some package outputs two identifying messages prefixed with ABD: then a microtype cfg file is input
(/usr/local/texlive/2018/texmf-dist/tex/latex/microtype/mt-cmr.cfg)
at this point TeX has finished typesetting page 1 and starts to output that page so you see [1 in the log, while generating the PDF for that page it needs to access some font data so you see (wrapped)
{/usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}
where {...} is a pdftex logging of an internal input as oppsed to the classic (...0 logging of an explicit input.
then you see ] denoting page 1 being finally shipped out.
TeX now presumably sees an input of your CS188Notes file and logs
(~/CS188Notes.tex
The chapter` command in there logs:
Chapter 2.
so up to this point everything is good, the messages are just informational.
Now we see
Overfull hbox (0.12741pt too wide) in paragraph at lines 27--29
So something is .1pt (not very much:-) too wide on the page after page 1 and on line 27 of the source file ~/CS188Notes.tex Te actual text is logged as
T1/cmr/m/n/12 (+20) brains are good at making rational. But the main problem i
s that brains are not modular
so it is that sentence, set in T1 (Latin) encoded computer modern medium weight, normal shape 12pt font, adjusted (+20) by microtype.
then somewhat strangely TeX logs
[7][8]
which means pages 7 and 8 got output (did you increment the page counter, what happened to pages 2 to 6 ?
Then another chapter command logs
chapter 3
So the only thing wrong is the text about brains where tex couldn't find an ideal line break, it's only .1pt so you could ignore it (if you set hfuzz to .2pt then TeX would not warn about this at all or you may want to adjust the typesetting (or wording) of that paragraph to help with line breaking.
answered Jan 5 at 0:09
David CarlisleDavid Carlisle
486k4111221867
add a comment |
The comments have pointed you at existing answers describing the general issue but I'll try to describe the log output you show (it would have been a lot easier if you had posted that as text not an image) but I OCR'd the image here:
(/usr/local/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
) (/usr/local/texlive/2018/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
(/usr/local/texlive/2018/texmf-dist/tex/latex/oberdiek/grfext.sty)
(/usr/local/texlive/2018/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
ABD: EverySelectfont initializing macros ABD: EveryShipout initializing macros
(/usr/local/texlive/2018/texmf-dist/tex/latex/microtype/mt-cmr.cfg) [1{/usr/loc
al/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]
(~/CS188Notes.tex
Chapter 2.
Overfull hbox (0.12741pt too wide) in paragraph at lines 27--29
T1/cmr/m/n/12 (+20) brains are good at making rational. But the main problem i
s that brains are not modular
[7] [8] Chapter 3.
The first thing to note is that TeX wraps the messages at a (user settable) width
and then whenever it input a file it logs ( followed by the file path, and when it finishes with that file and processing returns to the file that processed the input Tex logs ).
The graphics package internally does input{supp-pdf.mkii} which on your system gets logged as
(/usr/local/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
as that is the directory where the file was located. that file identifies itself with a message so then you see
[Loading MPS to PDF converter (version 2006.09.02).]
and a newline then that file is finished so you see ) At this point graphics inputs epstopdf-base.sty which in turn inputs grfext.sty and epstopdf-sys.cfg then you see )) as both levels of input have finished. Then some package outputs two identifying messages prefixed with ABD: then a microtype cfg file is input
(/usr/local/texlive/2018/texmf-dist/tex/latex/microtype/mt-cmr.cfg)
at this point TeX has finished typesetting page 1 and starts to output that page so you see [1 in the log, while generating the PDF for that page it needs to access some font data so you see (wrapped)
{/usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}
where {...} is a pdftex logging of an internal input as oppsed to the classic (...0 logging of an explicit input.
then you see ] denoting page 1 being finally shipped out.
TeX now presumably sees an input of your CS188Notes file and logs
(~/CS188Notes.tex
The chapter` command in there logs:
Chapter 2.
so up to this point everything is good, the messages are just informational.
Now we see
Overfull hbox (0.12741pt too wide) in paragraph at lines 27--29
So something is .1pt (not very much:-) too wide on the page after page 1 and on line 27 of the source file ~/CS188Notes.tex Te actual text is logged as
T1/cmr/m/n/12 (+20) brains are good at making rational. But the main problem i
s that brains are not modular
so it is that sentence, set in T1 (Latin) encoded computer modern medium weight, normal shape 12pt font, adjusted (+20) by microtype.
then somewhat strangely TeX logs
[7][8]
which means pages 7 and 8 got output (did you increment the page counter, what happened to pages 2 to 6 ?
Then another chapter command logs
chapter 3
So the only thing wrong is the text about brains where tex couldn't find an ideal line break, it's only .1pt so you could ignore it (if you set hfuzz to .2pt then TeX would not warn about this at all or you may want to adjust the typesetting (or wording) of that paragraph to help with line breaking.
answered Jan 5 at 0:09
David CarlisleDavid Carlisle
486k4111221867
The comments have pointed you at existing answers describing the general issue but I'll try to describe the log output you show (it would have been a lot easier if you had posted that as text not an image) but I OCR'd the image here:
(/usr/local/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
[Loading MPS to PDF converter (version 2006.09.02).]
) (/usr/local/texlive/2018/texmf-dist/tex/latex/oberdiek/epstopdf-base.sty
(/usr/local/texlive/2018/texmf-dist/tex/latex/oberdiek/grfext.sty)
(/usr/local/texlive/2018/texmf-dist/tex/latex/latexconfig/epstopdf-sys.cfg))
ABD: EverySelectfont initializing macros ABD: EveryShipout initializing macros
(/usr/local/texlive/2018/texmf-dist/tex/latex/microtype/mt-cmr.cfg) [1{/usr/loc
al/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]
(~/CS188Notes.tex
Chapter 2.
Overfull hbox (0.12741pt too wide) in paragraph at lines 27--29
T1/cmr/m/n/12 (+20) brains are good at making rational. But the main problem i
s that brains are not modular
[7] [8] Chapter 3.
The first thing to note is that TeX wraps the messages at a (user settable) width
and then whenever it input a file it logs ( followed by the file path, and when it finishes with that file and processing returns to the file that processed the input Tex logs ).
The graphics package internally does input{supp-pdf.mkii} which on your system gets logged as
(/usr/local/texlive/2018/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
as that is the directory where the file was located. that file identifies itself with a message so then you see
[Loading MPS to PDF converter (version 2006.09.02).]
and a newline then that file is finished so you see ) At this point graphics inputs epstopdf-base.sty which in turn inputs grfext.sty and epstopdf-sys.cfg then you see )) as both levels of input have finished. Then some package outputs two identifying messages prefixed with ABD: then a microtype cfg file is input
(/usr/local/texlive/2018/texmf-dist/tex/latex/microtype/mt-cmr.cfg)
at this point TeX has finished typesetting page 1 and starts to output that page so you see [1 in the log, while generating the PDF for that page it needs to access some font data so you see (wrapped)
{/usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}
where {...} is a pdftex logging of an internal input as oppsed to the classic (...0 logging of an explicit input.
then you see ] denoting page 1 being finally shipped out.
TeX now presumably sees an input of your CS188Notes file and logs
(~/CS188Notes.tex
The chapter` command in there logs:
Chapter 2.
so up to this point everything is good, the messages are just informational.
Now we see
Overfull hbox (0.12741pt too wide) in paragraph at lines 27--29
So something is .1pt (not very much:-) too wide on the page after page 1 and on line 27 of the source file ~/CS188Notes.tex Te actual text is logged as
T1/cmr/m/n/12 (+20) brains are good at making rational. But the main problem i
s that brains are not modular
so it is that sentence, set in T1 (Latin) encoded computer modern medium weight, normal shape 12pt font, adjusted (+20) by microtype.
then somewhat strangely TeX logs
[7][8]
which means pages 7 and 8 got output (did you increment the page counter, what happened to pages 2 to 6 ?
Then another chapter command logs
chapter 3
So the only thing wrong is the text about brains where tex couldn't find an ideal line break, it's only .1pt so you could ignore it (if you set hfuzz to .2pt then TeX would not warn about this at all or you may want to adjust the typesetting (or wording) of that paragraph to help with line breaking.
answered Jan 5 at 0:09
David CarlisleDavid Carlisle
486k4111221867
edited Jan 5 at 0:30
answered Jan 5 at 0:09
David CarlisleDavid Carlisle
486k4111221867
answered Jan 5 at 0:09
David CarlisleDavid Carlisle
486k4111221867
answered Jan 5 at 0:09
David CarlisleDavid Carlisle
486k4111221867
486k4111221867
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%2f468662%2fgeneral-question-how-do-understand-latex-warnings-and-errors-is-there-any-docu%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
2
Welcome to TeX.SE! I can only see warnings, no errors. (Generally you should not use screen shots for code or text output.) These things happen if LaTeX "thinks" that the line breaks have room for improvements. Depending on what you are doing (you do not provide the source code) providing the hyphenation of certain word in that line may already make this warning disappear. If you want more information, please provide a minimal working example that produces these warnings.
– marmot
Jan 4 at 23:23
1
Yes, we can google code that we can copy more quickly than code that we have to punch in. ;-) More seriously, you see that there are links on the right-hand side. They are generated based on the contents. If your contents contained "overfull", you would see more helpful links even when typing your question.
– marmot
Jan 4 at 23:29
1
Some people are not fortunate enough to be able to read the text in the picture, but they may well have software that can read text to them. It is also more convenient for people who can see the text in the picture when they can copy and paste parts of your error messages to explain them to you. Finally, web searches can pick up text, but are not (yet) great at picking up text from pictures.
– moewe
Jan 4 at 23:29
1
The LaTeX Companion has at the end a good overview over many error messages.
– Ulrike Fischer
Jan 4 at 23:30
1
When I did a quick google search with
site:tex.stackexchange.com overfull, I got dragged here, which IMHO provides some good information on parts of your question. In my experience, google searches withsite:tex.stackexchange.comin tend to be more efficient than searches with the tool provided by this site (unfortunately).– marmot
Jan 4 at 23:33