D'oh... Okay let me first say I'm a moron and I should think carefully about my posts at 3am... Sorry to waste your time with that...
Of course you are right there Lax, I had the syntax wrong, but it appears I am having a different problem which I will try to explain more clearly now
I can bind backslash fine from a session using this code
What I am trying to do however, is have the binds performed from the uplink to an arbitrary session at any time... What fails for me (and works for other keystrokes other than those containing a backslash) is the following:
Code: Select all
uplink relay is1 bind -press bindname \\ mycommand
This is what yields the "bind failed" error... In fact, if I try this in the uplink, it also fails:
Code: Select all
relay is1 bind -press bindname \\ mycommand
What is even more strange is if I first do this in the session:
This works as expected and I see this on the console:
Code: Select all
[bindname] [\] Command (Press): mycommand
And NOW, when I try to do this:
Code: Select all
uplink relay is1 bind -press bindname \\ mycommand
The binding doesn't fail but it doesnt bind the proper keystroke, the console on the uplink says:
Code: Select all
[bindname] [] Command (Press): mycommand
Thinking that it might be some double-unescaping that might be occurring by sending the command via relay, I even tried
Code: Select all
uplink relay is1 bind -press bindname \\\\ mycommand
But this does something else wrong, the console then says:
Code: Select all
[bindname] [" "mycommand] Command (Press):
Is there some trick to escaping when relaying a bind command to a session that I'm missing here?