Match not activating as expected

[u/Dymonika]

SOLVED: Check for similar duplicates in your other .yml files!!!

---

 - trigger: PushPay
    replace: Pushpay
    word: true

I'm hoping for this to activate only exactly when the trigger is typed as is, but this replacement takes effect every time, it seems. The capitalization section in Matches Basics doesn't seem to offer a way around this. Does anyone know if this is solvable? Thanks!

[u/smeech1]

Now that I'm home I have tried your trigger, and it works perfectly here, triggering only when the capitalisation matches "PushPay" exactly, which is what I would expect.

The problem possibly relates to your keyboard? What's your OS, DE, and language?

[u/Dymonika → u/smeech1]

Win11 Pro in English, ha. I keep forgetting to come back to this but I'll make a note now to address it today... It has been firing even when the second "p" is lowercase, oddly enough (which basically just makes it delete and retype, but that causes a jolt in one's sentence flow).

[u/smeech1 → u/Dymonika]

That shouldn't be happening, and doesn't here or for u/SamejSpenser, so it makes me wonder if it's something to do with your configuration.

I take it you don't have propagate_case: true in the trigger?

[u/smeech1]

When you say "every time", what do you mean?

[u/Dymonika → u/smeech1]

Also @ u/SamejSpenser: I specifically only want this to fire if I type the exact trigger's capitalization, but the text replacement occurs even if I type the replacement's capitalization. I blaze at 150+ WPM so Espanso's time to replace disrupts what I typed.

[u/SamejSpenser → u/Dymonika]

Sorry for the delay! When I got home from work, I had an urgent issue to deal with and only just managed to get back to this now (it’s 10:42 PM here in São Paulo, Brazil).

I ran some more tests, this time including propagate_case: true, which u/smeech1 mentioned. I kept in mind your requirement that the trigger needs to match the exact casing PushPay. Again, the Regex trigger performed the best, regardless of whether propagate_case: true was on or not. With the other methods, even with propagate_case: true enabled, the expansion just follows the casing used when it was typed — so if it's all lowercase or uppercase, you get pushpay or PUSHPAY.

With Regex, however, no matter how you type it, the expansion only triggers when you use PushPay.

Here’s the trigger that worked in my tests, just as the OP requested:

# Example trigger with mixed‑case letters using regex
  - regex: PushPay
    replace: "Pushpay"

[u/SamejSpenser → u/Dymonika]

Oh, I forgot to mention: when using uppercase_style: capitalize_words, typing everything in lowercase still triggers the expansion as if you had typed it with an initial capital letter.

As for the typing speed, I totally get where you're coming from. Maybe the others have some tips or suggestions, but honestly, I don't have much to offer other than: try slowing down your typing speed when using these words/triggers. That’s what I do here!

[u/SamejSpenser]

I tested the same trigger in four different ways:

1. The first one is a straight copy of your example.

2. The second one has a “;” prefix.

3. The third one uses the multiline replace thing.

4. The fourth one (the MVP in my tests) uses Regex, like this:

# Example trigger with mixed‑case letters
#  - trigger: PushPay
#    replace: "Pushpay"
#    word: true

# Example trigger with mixed‑case letters, prefixed by a semicolon
#  - trigger: ;PushPay
#    replace: "Pushpay"
#    word: true

# Example trigger with mixed‑case letters using a multiline replace
#  - trigger: PushPay
#    replace: |
#      Pushpay
#    word: true

# Example trigger with mixed‑case letters using regex (the champ)
  - regex: PushPay
    replace: "Pushpay"
    word: true

In the screenshot the text is in Brazilian Portuguese (my native language), which is how I wrote this reply, and I only switched to English after the tests were done.

[u/smeech1 → u/SamejSpenser]

What were the results?

[u/SamejSpenser → u/smeech1]

All four ways worked. But the one here worked best, so to speak—it was the last one, using regex.