-
Hi, I've tried to ssh with |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
@pmeheut Can you clarify a few things, please:
I wouldn't have expected for Clink to work over ssh. It has to use a virtual terminal input keyboard driver that interacts directly with the console input subsystem, and I don't see how that could work over ssh. But if you're saying that there are situations where Clink has its full capabilities when running over ssh, then can you share more information about that? I haven't used ssh, and I don't have access to an ssh server. My understanding is it essentially redirects stdin, stdout, and stderr across encrypted sockets. That won't have access to the console subsystem, and so input will be limited to letters and symbols and a subset of Ctrl codes. I don't know whether Lua scripts and prompt filtering would be expected to work. |
Beta Was this translation helpful? Give feedback.
-
Sorry: outrun is the spell-checker at work. I meant autorun. I understand your explanation and clink.log says: 05c8 start_logger 160 ---- 2022/12/06 06:16:22.592 ------------------------------------------------- |
Beta Was this translation helpful? Give feedback.
-
BTW, reading the clink.log gave me an idea and I found the solution. It has nothing to do with clink. I just needed to pass the '-t' option to ssh. This is unnecessary usually but here, with a command to run, it forces it to allocate a console subsystem. |
Beta Was this translation helpful? Give feedback.
BTW, reading the clink.log gave me an idea and I found the solution. It has nothing to do with clink. I just needed to pass the '-t' option to ssh. This is unnecessary usually but here, with a command to run, it forces it to allocate a console subsystem.
So everything works.
Thanks.