-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entire cvitem moves to a new page, if the number of lines exceed. #331
Comments
I'm having a similar issue but instead of a new page, the titles in the experience section move to the center |
Spanning multiple pages and keeping a table environment would require the use of @OJFord: #288, #331, and #341 are duplicates in so far as they are all issues related to the behavior of |
I'm having the same issue with a long publication list and am not sure how to apply longtable. Temporary solution:
|
As far as I know this is expected behavior for |
Hi everyone, an alternative solution that I use can be found in longtable section 5 pg 7 . Apparently
is equivalent to
So just replace if you want to use |
I tried implementing the solution shared by @h31nr1ch. While it fixed the issue with tables not breaking with page breaks, it introduced some issues such as extra space between rows and subsection headings. Therefore, I've adjusted it as follows: % Define an environment for cventry
\newenvironment{cventries_ltb}{%
\vspace{\acvSectionContentTopSkip}
\setlength{\LTleft}{0pt}
\setlength{\LTright}{0pt}
\setlength{\LTpre}{0pt}
\setlength{\LTpost}{-5pt}
\begin{longtable}{@{\extracolsep{\fill}} R{3.3cm} L{\textwidth - 3.7cm}}
}{%
\end{longtable}
}
\newcommand*{\addedu}[4]{%
\entrydatestyle{#4} & \entrypositionstyle{#1} \hfill \entrylocationstyle{#3}\\
& \entrytitlestyle{#2} \\
} Observations:
I hope this helps. I might be wrong or missing some easy solution, but so far I can only make this work. |
How do I prevent a cvitem from from moving to a new page, because of it's size, in the experience section?
The text was updated successfully, but these errors were encountered: