Bug Tracker

ID:150 🔗
Status:Closed (Fixed)
Submitted by:Nicola Talbot
Date:2020-02-11 18:36:19
Summary:\glsentry... commands in section headings causes an error with undefaction=warn (or record) option


When an entry is undefined, commands like \glsentryname expand to \csname ...\endcsname forms. This can lead to undefined commands in the table of contents (toc) or list of figures/tables (lof/lot) files.
! Undefined control sequence.
<write> ...protect \numberline {1}\glo@lorem@name 
                                                  }{\thepage }\protected@fil...
This isn't an issue with the base glossaries package as it doesn't allow the referencing of undefined entries, and so isn't considered a bug with just glossaries.sty.

With glossaries-extra, the undefaction=warn package option (which is automatically implemented by the record option) allows for the referencing of undefined commands that trigger warnings rather than errors. This is essential with bib2gls as the entries are never defined on the first LaTeX call in the build process.

The glossaries-extra package does actually provide commands that are specifically designed for the use in captions and section headers (\glsfmtname etc) so these should typically be used rather than \glsentry.... However, with undefaction=warn the package should gracefully allow \glsentry... in captions and section headings if there's some particular reason to use them over the equivalent \glsfmt....









Fixed in v1.42.

Add comment or return to search results.

Watch This Report

If you would like to be notified whenever updates are made to this report, please fill in your email address in the box below and click on "Notify Me of Changes" button. (Please ensure the address is valid.) Your details won't be passed on to third parties in line with this site's Privacy Policy.

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).

E mail:
Confirm E mail:
Confirm Bug ID:

To unsubscribe from all notifications use the notifications page.


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).

(Optional. If provided, it will be shown with the comment.)
Confirm Bug ID:

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:
[li]first item[/li]
[li]second item[/li]

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

Click on the Preview button to preview the message.

Return to search results.