Jason Gauci
Is it an error we can catch and retry?
Interesting, thanks for the clear issue description. I don't believe ip addresses are supported at all. I think what's happening is the "10.96.0.1" is being passed to stoi and turned...
Hmm. Maybe the issue is that doing an et inside of an ssh has a problem? et always allocates a psuedoterminal so it doesn't need a -t. Ptys are cheap...
A lot of what you are describing is solved by -x, but I understand that -x limits you to one remote session per user/host pair. The bigger problem is, how...
The configurable timeout sounds pretty simple. The etterminal processes could fetch it from the cfg and kill themselves so no communication is even needed for that one. Happy to review...
Right here: https://github.com/MisterTea/EternalTerminal/blob/master/src/terminal/UserTerminalHandler.cpp#L71 You would read the cfg file for the timeout (look in the code for .cfg to see how to read the file), then keep the latest time...
On Mac, we need to install etterminal to /usr/local/bin instead of /usr/bin and this breaks the default flow. There's a command line parameter on the client you need to pass...
Is this issue still present in 6.2.9?
Hmm, as the thread suggests, I'm not using libtinfo5, but maybe it's coming it through ncurses-dev? On Wed, Mar 6, 2024, 3:12 PM Cliff Hill ***@***.***> wrote: > Any update...
Maybe I'm missing/forgetting something, but I don't see libtinfo5 mentioned anywhere in the repo?