# Bug Tracker

ID 111 Closed (Fixed) glossaries v4.24 \newglossaryentry nonumberlist fails on 2nd & later runs

## 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:
\glossaryentry{Baz?\glossentry{baz}...

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)

Geoffrey Jones

### MWE

\documentclass{article}

\usepackage{glossaries}
\makeglossaries

\begin{document}

\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

\end{document} 

## Evaluation

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.

## Watch This Report

If you supply your name, it will be used in the email greeting, which provides a more personal message, otherwise you'll just get a generic greeting. If you have previously supplied your name when signing up for notifications, you don't need to resupply it unless you want to change it.

If you have previously subscribed to notifications for this report, you can unsubscribe by clicking on the "Stop Notification" button.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

Name: (Optional.)

## Comment

You can append a comment to the report using the form below. Comments are checked first before being added. Any spam or offensive content will be removed first according to this site's Terms of Website Use. Please bear in mind that I develop and maintain free software in my spare time. If you want commerical level support then you can hire a TeX consultant.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

Name: (Optional. If provided, it will be shown with the comment.) Message: You can use the following markup: [pre]Displayed verbatim[/pre] [tt]monospace text[/tt] [em]emphasized text[/em] [b]bold text[/b] [url]web address[/url] Ordered list: [ol] [li]first item[/li] [li]second item[/li] [/ol] Unordered list: [ul] [li]first item[/li] [li]second item[/li] [/ul]

Click on the Preview button to preview the message.