Bug Tracker RSS feed

ID 214🔗
Submitted by: Nicola Talbot 🦜
Date: 2022-10-26 14:16:50
Last update: 2022-10-26 14:19:59
Status Closed (Not a Bug)
Category glossaries
Version 4.50
Summary Command \glossaryentryfield undefined

Return to Search Results

Sign in to subscribe to notifications about this report.

Description

When updating to glossaries v4.50, I get an error:
Command \glossaryentryfield undefined

MWE

Download (843B)

% arara: pdflatex
% arara: makeglossaries if found("aux", "@istfilename")
% arara: bib2gls: {group: on} if found("aux", "glsxtr@resource")
% arara: pdflatex
% arara: pdflatex if found("log", "Rerun to")
\documentclass{article}

\usepackage{glossaries}

\makeglossaries
\loadglsentries{example-glossaries-parent}

\newglossarystyle{mystyle}%
{%
  \renewenvironment{theglossary}{\begin{itemize}}{\end{itemize}}%
  \renewcommand*{\glossaryheader}{}%
  \renewcommand*{\glsgroupheading}[1]{}%
  \renewcommand*{\glossaryentryfield}[5]{%
   \item \glstarget{##1}{##2} (##3) ##4\glspostdescription\space ##5%
  }%
  \renewcommand*{\glossarysubentryfield}[6]{%
   \item \quad\glstarget{##2}{##3} (##4) ##5\glspostdescription\space ##5%
  }%
  \renewcommand*{\glsgroupskip}{}%
}

\begin{document}
\glsaddall
\printglossary[style=mystyle]
\end{document}

Evaluation

This is not a bug. In version 4.50, all commands and options that have been deprecated for over 6 years have been removed. You will need to use rollback if they are still required, but it's better to use the newer commands instead. See After updating to glossaries v4.50 I'm getting undefined commands or options errors (e.g. \glossaryentryfield) for further details.

Comments

0 comments.


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. All guest comments have to be manually checked before they appear on the page. There are too many bots trying to spam the site to allow unauthenticated users to post without verification.

Comment:


You can use the following markup:

Block:

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

In line:

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

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

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

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

Page permalink: https://www.dickimaw-books.com/bugtracker.php?key=214

Return to Search Results