Latest news 2021-06-05: New blog post: Dickimaw Books Site Account.

Bug Tracker

ID 111🔗
Date: 2016-06-07 21:21:49
Status Closed (Fixed)
Category glossaries
Version v4.24
Summary \newglossaryentry nonumberlist fails on 2nd & later runs

Sign in to subscribe to notifications about this report.


First run of pdflatex(*) on MWE with \newglossaryentry containing nonumberlist=true generates .glo file containing:
\glossaryentry{Baz?\glsnonextpages \glossentry{baz}...
Independent of whether the .gls file is then created with makeglossaries or whatever (i.e., in the simplest instance just rerunning pdflatex), second and subsequent runs of pdflatex on same MWE generates .glo file containing:
Ultimately, the nonumberlist instruction attached to individual new glossary entries is lost across multiple pdflatex runs.

(*) Command Line: pdflatex.exe -recorder --interaction=errorstopmode "glossariestest.tex"

pdfTeX, Version 3.14159265-2.6-1.40.17 (MiKTeX 2.9 64-bit) (preloaded format=pdflatex 2016.5.12) 8 JUN 2016 12:05

Package: glossaries 2016/05/27 v4.24 (NLCT)


Download (515B)




\newglossaryentry{foo}{name=Foo, description={always first}}
\newglossaryentry{bar}{name=Bar, description={may only succeed foo}}
\newglossaryentry{baz}{name=Baz, description={optional, after baz}, nonumberlist=true}

\gls{foo} is a variable. \gls{bar} is too. However, \gls{baz} is a functional.

% commented out the following line to simplify the MWE (uncomment if you like)...
% \printglossaries



It looks like this is the result of defining the entries in the document environment rather than in the preamble. It seems that the nonumberlist option isn't being written to the .glsdefs file, so it's not set on the next LaTeX run. I'll get that fixed in the next version, but I recommend moving the definitions to the preamble instead.

Update 2016-06-09 19:56 BST: fixed in version 4.25. Please allow a few days for it to get into the TeX distributions. You'll need to delete the .glsdefs file before rebuilding with the new version.



Add Comment

Name (optional):

Are you human? Please confirm the bug report ID (which can be found at the top of this page) or login if you have an account.


You can use the following markup:


[pre]Displayed verbatim[/pre]
[quote]block quote[/quote]

In line:

[file]file/package/class name[/file]
[em]emphasized text[/em]
[b]bold text[/b]
[url]web address[/url] [sup]superscript[/sup]

Ordered list:
[li]first item[/li]
[li]second item[/li]

Unordered list:
[li]first item[/li]
[li]second item[/li]

You can use the Preview button to review your message formatting before submitting.

Page permalink: