et needs ssh's -t option to support running tmux with et about eternalterminal

[timotheecour]

EDIT: my setup was a bit more complex and i needed a --jumphost host_aux, and what i had tried was:

from macos:

ssh host_aux
then this failed: et myhost -c "/pathto/tmux new-session -A -s foo"
while this worked: `et myhost` followed by `/pathto/tmux new-session -A -s foo`

but this works if I run directly:
et myhost --jumphost host_aux -c "/pathto/tmux new-session -A -s foo"

so there's a valid workaround, feel free to close if remaing bug is bearable

[MisterTea]

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 enough that no one has complained yet.

…

On Wed, Feb 21, 2024, 9:28 PM Timothee Cour ***@***.***> wrote: EDIT: my setup was a bit more complex and i needed a --jumphost host_aux, and what i had tried was: from macos: ssh host_aux then this failed: et myhost -c "/pathto/tmux new-session -A -s foo" while this worked: `et myhost` followed by `/pathto/tmux new-session -A -s foo` but this works if I run directly: et myhost --jumphost host_aux -c "/pathto/tmux new-session -A -s foo" — Reply to this email directly, view it on GitHub <#620 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACK5P2QTG4FXVC2Y5BAEYDYU23PBAVCNFSM6AAAAABDUEH3TWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJYGU4TAOJSG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>