Royal Apps

Disconnections can interrupt a terminal session, and sometimes it is important to see the history of what happened in the shell before the disconnection occurred. I have "Keep disconnected tabs open" enabled and "Close tab when session end" disabled, yet after reconnect the terminal buffer is cleared. I don't know whether this happens by design or due to a bug.

@Felix can you check how apps like ConEmu/Kitty/Putty do it? Even after they get disconnected, if you ask for a re-connect, you keep the buffer as was.

I'm looking for a replacement for Xshell on the Mac platform, and Royal TSX is the best choice so far, but I don't understand since we use iTerm 2 as the terminal plug-in,  why automatically clear the buffer when disconnected.  iTerm 2 is not designed to do that.  I hope the author can seriously consider this feature, after all, most of the products in the market don't do this, users have this need, at least add a switch for users to decide if they want to empty it or not. I'm looking forward to seeing this feature implemented in a future update. Thank you.

Hello Felix, 

Any further update on this topic? 

This is a very important feature, which is supported by other competing products. Hopefully it will be implemented. Very important for users with bad networks, such as firewalls that cause frequent disconnections and can lose context.

Regards, 

Vincent

I agree with previous posts. I was just about to add this as a feature request myself. It's extremely annoying that the screen and buffer is cleared when reconnecting.

Sure, when doing "restart session" in the menu in iTerm2, it also resets the terminal. Perhaps it is the same "function" it does in Royal TSX too. But the question is if it is possible for Royal TSX to keep the buffer and screen.

Would also love to have this option, when reconnecting - to keep the previous history opened.

This missing feature is the only thing stopping me from purchasing a license. Being able to keep the history after a (accidental) disconnect is essential for me.

Please reconsider the design if possible.

I also need this feature, I got the license thinking I would get the same features and maybe more than MobaXTerm but for Mac, however, it looks like it isn't the case. I can't seem to find a way to make this happen. Keeping the buffer even after a connection closes is a must.

Hi everyone, my current solution for this is to use the Logging feature, as it can redirect all the buffers to a file in real-time. So when the session gets disconnected accidentally, I can still access the previous logs in the log files.

I don't mind that this is the default, but a checkbox to disable this feature would be most welcome. The logging work around is "OK" but not always the best thing for workflow.