\cvsubentry extra alignment and misplaced \omit fix #335
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using \cvsubentries and \cvsubentry elements, XeLaTex compiler raises the below errors:
Extra alignment tab has been changed to \cr.
[...]
You have given more \span or & marks than there were
in the preamble to the \halign or \valign now in progress.
So I'll assume that you meant to type \cr instead.
OverLeaf hint:
You have written too many alignment tabs in a table, causing one of them to be turned into a line break. Make sure you have specified the correct number of columns in your table.
Misplaced \omit.
\multispan ->\omit
@multispan
[...]
I expect to see \omit only after tab marks or the \cr of
an alignment. Proceed, and I'll ignore this case.
First error seems to be caused by a missing new line command inside the \cvsubentry declaration on awesome-cv.cls.
This piece of code:
should become:
Second issue, seems to be related to a problem between
\ifthenelse
and\multicolumn
.As stated here,
\multicolumn
must be the first thing TeX sees in a table cell, after expanding commands; unfortunately, the workings of\ifthenelse
leave something before\multicolumn
when the test is computed false.A good solution could be to use a different test making command.