Latest news 2024-03-02: Ebook sale (3rd–9th March 2024): short story cybercrime fiction Unsocial Media free; short story noir crime fiction I’ve Heard the Mermaid Sing free; crime fiction novel The Private Enemy US$1.99; illustrated children’s story The Foolish Hedgehog US$0.99. For further details, see latest blog post.

Bug Tracker RSS feed

I’m currently working on a major new version of the datatool package. This may take a while. Please be patient. (Experimental version available for testing.)

ID 88🔗
Date: 2015-05-06 04:20:51
Status Closed (Not a Bug)
Category glossaries
Version 4.15
Summary Groups not working for sort=def
OS Windows 7

Sign in to subscribe to notifications about this report.


When using glossaries with sort=def and style=alttreehypergroup, groups are not recognized any more and the output is broken.

Glossaries version: 4.15

This bug was reported on TEX.SX, too (includes images of the expected and actual output): Glossaries: Groups not working


Download (820B)

% arara: pdflatex: { action: nonstopmode }
% arara: makeglossaries
% arara: pdflatex: { action: nonstopmode }
% arara: pdflatex: { action: nonstopmode }

% \usepackage[style=alttreehypergroup, symbols, nolong, nosuper, nonumberlist]{glossaries}

\usepackage[sort=def, style=alttreehypergroup, symbols, nolong, nosuper, nonumberlist]{glossaries}


\newglossaryentry{firstgroup}{name={firstgroup}, description={\nopostdesc}}
\newglossaryentry{aaa}{name={aaa}, description=abcd, parent=firstgroup}

\newglossaryentry{secondgroup}{name={secondgroup}, description={\nopostdesc}}
\newglossaryentry{bbb}{name={bbb}, description=abcd, parent=secondgroup}



I've put a more detailed response in my answer on TeX.SX, but this is a feature rather than a bug due to the fact that the sort=def key changes the sort key for each entry to a numerical value, so all entries end up in the "Numbers" group. You can get around it by switching to "Option 1" and passing the sort=def to \printnoidxglossary.



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: