Trigger text remains with citrix receiver on Windows 10

[wressl]

When using a Citrix app on Windows 10 the trigger text is not replaced, but remains along with the expansion. When using the same Citrix app on MacOS it works perfectly

For example: On MacOS :espanso becomes "Hi There!" on Win10 :espanso becomes ":espansoHi there!"

Also, if backend is set to Clipboard, no expansion happens at all. It works perfectly in other Windows apps like Notepad, so I believe this is specific to Citrix. I am using the latest Citrix receiver (4.12). I would suppose there is some permissions issue that is preventing espanso from deleting the trigger text but do you have any idea how to fix it?

[federico-terzi]

Hey @wressl,

It seems like Citrix can't detect the first sequence of "backspace" that is used to delete the trigger. Does Citrix require Admin privileges? Also if you type backspace manually, does it work correctly?

Cheers :)

[wressl]

Normally citrix does not require admin privileges.
I tried running as admin and this did not make any difference. Backspace manually definitely works correctly. Is there a way to log the key commands being sent by the keyboard to citrix vs espanso?

[federico-terzi]

Thank you @wressl, most probably the problem is that espanso sends the delete events too fast for Citrix. In the next few days I'm going to send you a modified version of espanso that slows the deletion down, so that you can tell me whether it works correctly. Once we are able to track down the problem, we can find a solution!

Cheers :)

[federico-terzi]

Hey, I'm currently shipping espanso 0.6.0 which includes an option that could solve your problems! Could you please try to add the following line to your default.yml file:

backspace_delay: 10

and see if that helps on Citrix? Also try to increase that number if you see any other error.

Note that this line slow down espanso for all applications (which is not desirable), so if it works correctly we can then apply it only to Citrix by defining an app-specific configuration.

Let me know if that helps :)

[wressl]

Unfortunately I don't see any improvement with changing backspace_delay. I tried 1, 10, 100, 1000 and can definitely see the delay at the higher numbers. Interestingly when I increase it to 100, the trailing space also remains ":espanso Hi there!" instead of ":espansoHi there!" I'm not sure if that might provide some kind of clue. I'm looking into logging in Citrix and will let you know if I can produce anything meaningful.

[federico-terzi]

Too bad, I thought it could help as it solved a similar problem in another application. It seems like this problem is related more to Citrix that espanso. If I can get my hands on a Citrix installation I'll make some tests myself and let you know.

Cheers :)

[madmunky]

Was there ever any fix for this as I have the same issue, I've tried the backspace_delay: 10 option without any luck

[wressl]

No fix that I’m aware of. The problem is the same with other text expanders like aText or AutoHotKey so it is not unique to espanso. Effectively makes it impossible to use on my Windows + Citrix combination.

On Aug 13, 2021, at 6:55 AM, Chris Richardson @.***> wrote:

Was there ever any fix for this as I have the same issue, I've tried the backspace_delay: 10 option without any luck

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/federico-terzi/espanso/issues/246#issuecomment-898438164, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOLL7US3HT4EFEJELOTDO4DT4UI27ANCNFSM4MOPYMOQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

[crontol]

This is quite annoying.

I have to change back to TextExpander and it works with Citrix.

https://textexpander.com/blog/textexpander-is-citrix-ready

[progS1m]

This is so bad, would be so helpful to get this addressed :-( none of the parameters do work unfortunately.

[YamiTL]

Thank you for bringing this to our attention! After review, we've determined that this issue isn't a high priority for our immediate roadmap. We're closing it for now to focus on more critical items, but we appreciate the suggestion and will revisit it if our priorities shift.