Latest news 2021-09-06: new blog post "Legacy Documents and TeX Live Docker Images".

# Feature Tracker

ID 26🔗 2014-10-09 09:58:30 Closed (Implemented) Sign in if you want to like this report. glossaries create link, but no link target by \gls macros

## Description

I have the problem with dual entries (p 106 in manual) but it may be a feature in other places, too.

I have reverences from the list of acroyms to glossary and vice versa. These appear in the numberlist, which is not very clever.

It is possible to kill the hyper feature for a \gls macro completely, but ist is not possible to shut down one of the two aspects (for my problem, the second):

• creating a link to a glossary entry
• and
• being a link target and my page number is appearing in the number list in the glossary

I think it would be very neat to being able to define

\gls[hyper=true, innumberlist=false]{OMG}

Or even make this the standard whilst being in the \begin{theglossary} environment

Stefan

No mwe.tex

## Evaluation

This feature is now available with glossaries-extra.sty where you can use the boolean key noindex within the optional argument of commands like \gls to suppress indexing.

🔗Comment from Stefan
Date: 2014-10-10 11:21:55

after fiddeling around with my example**, I figured out, that it is vital that innumberlist=false is the standard option in \begin{theglossary}, because the targets are placed, even if there are no links in the name-items (name=#4 in glos and #3 in acr)

\newcommand*{\newacroglossentry}[5][]{ %
\newglossaryentry{#2__}{ %
name={#4}, %
description={(#2) #5}, %
#1} %
}

\newacroglossentry{N}{N}{a number}{precessor of \glsname[innumberlist=false]{NPO}}

\newacroglossentry{NPO}{N+1}{another number}{successor of \glsname[innumberlist=false]{N}}


** desired link structure is (works despite of the nonumberlist-issue):
first to glos
next to acr

acrdesc to glos (no numberlist item)
acrnumberlist to first and next

glosdesc-usedacr to acr (no numberlist item)
glosdesc-usedglos to glos (no number list item)
glosnumberlist to first and next

Name (optional):

Are you human? Please confirm the feature request 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.

🔗Comment from Nicola Talbot 🦜
Date: 2014-10-30 00:00:00

It sounds as though you just need to use \glshyperlink, which creates a hyperlink but doesn't add a line to the glossary file. If this is the case, then I can close this as already implemented.

Name (optional):

Are you human? Please confirm the feature request 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.

🔗Comment from Stefan
Date: 2016-01-03 20:31:28

thanks for watching over my request. I now accidentally found it again after failing to find it while searching.

I helped myself by creating macros using \glshyperlink as you wrote here.

the full code was in the end:

\newcommand*{\newacroglossentry}[5][]{ %
\newglossaryentry{#2__}{ %
name={#4}, %
description={(#3) #5}, %
#1} %
}

}

}

}

}

}


still, using macros other than \gls is a bit a pain

Name (optional):

Are you human? Please confirm the feature request 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.

🔗Comment from Nicola Talbot 🦜
Date: 2016-01-05 09:53:00

This feature will be added to the pending glossaries-extra package, which is currently only available in the experimental code page.

Name (optional):

Are you human? Please confirm the feature request 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.

Name (optional):

Are you human? Please confirm the feature request 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.