Quick Bangs are used even when they shouldn't be

firegore

I have the default Bangs defined as Quick Bangs "g w r hn yt"
The Description clearly says they should only activate when they are follow by a space.

However it also activates when the Quick Bang is at the end of the Search query e.g. "kagi searches wikipedia when search term includes w" opens Wikipedia Search, instead of Kagi Search.
This is not what the Documentation of the Feature says, is this an undocumented Feature or a Bug?
Its especially noticeable when you search for things like "Raspberry Pi Zero 2 W" and it redirects you to Wikipedia.

I expect it to either be documented or as currently designed, open the Kagi Search instead of Wikipedia (or other Quick Bang searches)

Jesal

Maybe we're looking at different descriptions, but I believe the description on the setting page is just showing an example of how quick bangs can be used and not indicating that this is the only way quick bangs can be used:

Allow use of the following bangs without the '!' character. For example 'r' followed by a 'space' will activate a search on Reddit. 20 allowed maximum

I hope they don't actually change the functionality for this though. I typically use quick bangs at the end of my queries so having to add an additional space afterwards isn't really much different than just using a regular bang

firegore

If it's intended or not, the Documentation is still wrong, as if you take it the Documentation fully, this would mean it would also trigger when the bang is in the middle of the Search Query, which is not what happens (would be stupid anyways if it works like that).

Jesal

firegore The current documentation for bangs shows that they can only be used at the start or end of a query

firegore

Jesal Thanks for pointing that out, the Documentation indeed says that, i ment the little Paragraph on the Settings Page, thats what confused me in the first Place.

I didn't even know there's a whole Help / Docs Page for that Feature.

Luis

I see that @Jesal has already answered @firegore query (thank you!). I'll mark this thread as nofix unless you'd like to suggest an alternative approach. Please feel free to follow up in this thread.