Smile for the Camera: a new cybercrime short story ebook.

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 173🔗
Date: 2021-06-08 07:42:45
Status Closed (Fixed)
Category glossaries
Version 4.46
Summary .glsdefs is not updated

Sign in to subscribe to notifications about this report.

Description

Following are the steps to reproduce:
  1. Compile minimal working example
  2. Change the test glossary entry's description
  3. Compile minimal working example
  4. Compile minimal working example
Expected behavior: The new description should show up in the document.

Actual behavior: The old description shows up in the document.

While the documentation states "if you modify an entry definition, you need a second run to see the effect of your modification", this does not help.

Possible root of the bug:

\newrobustcmd{\new@glossaryentry}[2]{%
  \ifundef\@gls@deffile
  {%
     \global\newwrite\@gls@deffile
     \immediate\openout\@gls@deffile=\jobname.glsdefs
  }%
  {}%
  \ifglsentryexists{#1}{}%
  {%
     \gls@defglossaryentry{#1}{#2}%
  }%
  \@gls@writedef{#1}%
}
By using \ifglsentryexists, the new dfinition is not used. Not even for \@gls@writedef.

MWE

Download (176B)

\documentclass{report}
\usepackage{glossaries}
\makeglossaries
\begin{document}
\newglossaryentry{test}{name={t},description={Test2}}
\Glsentrydesc{test}
\end{document}

Evaluation

Fixed in v4.47. (You may need to delete your .glsdefs file after upgrading.)

Note that this update slightly changes the format of the .glsdefs file. If anyone has a system that parses this file (for example, to pick up labels for autocompletion) it will need to be modified.

Old format:

\ifglsentryexists{label}{}%
{%
\gls@defglossaryentry{label}%
{%
key value list
}%
}%
New format:
\glsdefs@newdocentry{label}%
{%
key value list
}%

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.

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=173