# \[bug\] Secondary keywords do not work?

**URL:** <https://discussion.listary.com/t/bug-secondary-keywords-do-not-work/9551>\
**Category:** Bug Reports\
**Created:** [October 21, 2024, 3:42pm UTC](https://discussion.listary.com/t/bug-secondary-keywords-do-not-work/9551 "2024-10-21T15:42:04Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![craziedde](https://discussion.listary.com/letter_avatar_proxy/v4/letter/c/ee7513/32.png) [@craziedde](https://discussion.listary.com/u/craziedde)\
**Post date:** [October 21, 2024, 3:42pm UTC](https://discussion.listary.com/t/bug-secondary-keywords-do-not-work/9551/1 "2024-10-21T15:42:04Z")

</div>

Hi,

Please see question in the screenshot below:

 ![image](https://discussion.listary.com/uploads/default/original/2X/8/852bad17c040153a923714bae48811096eb39b0a.png)

@craziedde

---

<div class="post-metadata">

**Author:** ![horst](https://discussion.listary.com/letter_avatar_proxy/v4/letter/h/edb3f5/32.png) [@horst](https://discussion.listary.com/u/horst)\
**Post date:** [October 22, 2024, 8:29am UTC](https://discussion.listary.com/t/bug-secondary-keywords-do-not-work/9551/2 "2024-10-22T08:29:36Z")

</div>

I would never expect that this is resolved as a keyword.  
I don’t see the logic behind this request to use sub-strings of keywords ?  
Typing any words leads to searches and not recognizing as keywords.

---

<div class="post-metadata">

**Author:** ![craziedde](https://discussion.listary.com/letter_avatar_proxy/v4/letter/c/ee7513/32.png) [@craziedde](https://discussion.listary.com/u/craziedde)\
**Post date:** [October 22, 2024, 11:59am UTC](https://discussion.listary.com/t/bug-secondary-keywords-do-not-work/9551/3 "2024-10-22T11:59:39Z")

</div>

Hi @horst

Thank you for quick reply  
How to add SECOND keyword? (without creating second duplicate entry to same “command”)

---

<div class="post-metadata">

**Author:** ![xinyi](https://discussion.listary.com/user_avatar/discussion.listary.com/xinyi/32/4673_2.png) [@xinyi](https://discussion.listary.com/u/xinyi)\
**Post date:** [October 23, 2024, 9:35am UTC](https://discussion.listary.com/t/bug-secondary-keywords-do-not-work/9551/4 "2024-10-23T09:35:39Z")

</div>

Sorry, this feature isn’t available. It’s not possible to add a second keyword.

---

<div class="post-metadata">

**Author:** ![craziedde](https://discussion.listary.com/letter_avatar_proxy/v4/letter/c/ee7513/32.png) [@craziedde](https://discussion.listary.com/u/craziedde)\
**Post date:** [October 24, 2024, 12:12pm UTC](https://discussion.listary.com/t/bug-secondary-keywords-do-not-work/9551/5 "2024-10-24T12:12:25Z")

</div>

I think this is a “must” feature for this type of application

---

<div class="post-metadata">

**Author:** ![horst](https://discussion.listary.com/letter_avatar_proxy/v4/letter/h/edb3f5/32.png) [@horst](https://discussion.listary.com/u/horst)\
**Post date:** [October 24, 2024, 1:25pm UTC](https://discussion.listary.com/t/bug-secondary-keywords-do-not-work/9551/6 "2024-10-24T13:25:10Z")

</div>

Tell us one application (search tool) which does this ?

The only solutions are tools which sets aliases if certain strings are typed.  
I use QAP which allows this.  
Of course, you have to define each sub-string as an alias for your command.

---

<div class="post-metadata">

**Author:** ![craziedde](https://discussion.listary.com/letter_avatar_proxy/v4/letter/c/ee7513/32.png) [@craziedde](https://discussion.listary.com/u/craziedde)\
**Post date:** [October 24, 2024, 3:33pm UTC](https://discussion.listary.com/t/bug-secondary-keywords-do-not-work/9551/7 "2024-10-24T15:33:33Z")

</div>

> [@horst](#):
>
> Tell us one application (search tool) which does this ?

There are very low number of alternatives for this type of application.  
And I’m not sure if this is help to resolve the requested feature

> [@horst](#):
>
> The only solutions are tools which sets aliases if certain strings are typed.  
> I use QAP which allows this.  
> Of course, you have to define each sub-string as an alias for your command.

The only true solution to this problem (I in my view) is to simply create a duplicate “command” which is what I’m doing… but it’s less elegant solution, that is why I created this request.

@craziedde