Paul Gaborit
Paul Gaborit
The name could be `inner style`, `inner theme`, `type`, `option`, `kind`, `design`, `appearance`, `meta key`...
The macro approach is less user friendly. With a `style` (or any other name) key, you can use `style=beautiful table` or `style=old style`... With macro approach, you must use `\mytblrstylebeautifultable`...
Could the correct value of `\@tempdimb` be automatically deduced from dimensions of the chosen font?
This issue is related to this other issue: https://github.com/josephwright/beamer/issues/595
This bug has been detected several times: 1. https://tex.stackexchange.com/questions/130643/nested-itemize-environment-affects-vertical-spacing-of-parent-itemize-environmen 2. https://tex.stackexchange.com/questions/640148/nested-lists-consistent-vertical-spacing-with-beamer I propose another way to solve it: ``` \usepackage{etoolbox} \pretocmd{\itemize}{\vskip 0pt}{}{} \pretocmd{\enumerate}{\vskip 0pt}{}{} ``` or: ``` \usepackage{etoolbox} \makeatletter \pretocmd{\itemize}{\ifhmode\unvbox\voidb@x\fi}{}{}...
related issue: #530 #306
related issue: #519
We can also consider that it is a defect of `latexmk`. A first workaround is to tell `latexmk` to ignore `.luc` files via the following line in a `latexmkrc` file:...
Everything seems perfect. Thank you so much!
Extract from documentation of `\GenRefcontextData`: [...] _e.g. to sort citations with the `sortcites` option when the sorting of citations requires a different refcontext to that used for the actual reference...