5

The following MWE (borrowed from varioref: \vref or \vpageref at page boundary (may loop)) shows that \vref and \vpageref (from varioref) at page boundary are reported by errors (or warnings if \vrefwarning is placed in the preamble):

Package varioref Error: \vref or \vpageref at page boundary [...] (may loop).

But, if cleveref is loaded, there is no report even in case of loops (as that happens with the MWE if the line % \usepackage{cleveref} is commented out).

Do you see how to get the report even if cleveref is used?

\documentclass[12pt]{article}
\usepackage{blindtext,varioref}
% \usepackage{cleveref}

\makeatletter
\@ifpackageloaded{cleveref}{%
  \newcommand{\crossref}{\vref{tab:example}}
}{%
  \newcommand{\crossref}{table \vref{tab:example}}
}%
\makeatother

\newcommand{\test}{%
  \blindtext[3]

  These words are only for demonstration purposes. These words are only for
  demonstration purposes. These words are only for demonstration purposes. These
  words are only for demonstration purposes. These words are only for
  demonstration purposes. These words are only for demonstration purposes. These
  words are only for demonstration purposes. These words are only for
  demonstration purposes. These words are only for ... See \crossref

  \begin{table}[htbp]
    \centering
    \begin{tabular}{l}
      Test\\
    \end{tabular}
    \caption{Example Table}
    \label{tab:example}
  \end{table}
  \blindtext
}

\begin{document}
\test
\end{document}
  • 1
    Looks like there's a bug in cleveref's modification of \vref. You may want to contact the author of cleveref (email address at bottom of first page of the package's user guide) and draw his attention to this issue. – Mico Jan 25 '16 at 18:44
  • 1
    @Mico Author's attention drawn. – Denis Bitouzé Jan 27 '16 at 15:34
1

This might have been related to this bug, which should now be fixed in the latest version (0.19.3) available from my web site. At least, your MWE with cleveref enabled now produces the page-boundary warning.

  • Indeed, thanks! Regarding warning versus error, why not letting cleveref follow the varioref's behavior (error by default and warnings if, and only if, \vrefwarning is placed in the preamble)? – Denis Bitouzé Aug 26 '16 at 16:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.