Improving Search Efficiency for 'min (float)' in Node Selection

[kiruru002]

I often mistake [minus (float)] for [min (float)
When I search for a node from a float and type [min], the most likely completion candidate is [minus] (Subtract).
(The cursor is on Subtract instead of min from the beginning.)
Am I wrong?
What do you think of this search window?
It is my convention to type min to get min
Is there a fastest way to get min (float)?

Any help on how to work around this would be appreciated!

Translated with DeepL.com (free version)

[BIGTIMEMASTER (Aljav)]

if you click the star icon it will be favorited, and then favorites will show up top in the search

[pezzott1]

Just type -, +, *, / .

[kiruru002]

I found this setup
Really helped me
Thank you!

[/Script/Kismet.BlueprintPaletteFavorites]
CustomFavorites=(FieldName="/Script/Engine.KismetMathLibrary:FMin",NodeName="/Script/BlueprintGraph.K2Node_CommutativeAssociativeBinaryOperator")

[kiruru002]

I’m not sure I understand.
What I want is the [min (float)] node

[pezzott1]

My bad. I understood something else.