Ever since moving to eshell+tramp, all of these persistence tools, however beautifully designed, somehow strike me as solving the wrong problem.
Could you elaborate on this setup?
Eternal Terminal
51–60 of 104 posts
Re: Eternal Terminal
#52Earlier quoted context omitted.
> Been waiting for a good replacement for tmux to come along for a while now that isn't just i3 > Does anyone else have a love hate relationship with tmux? > I hate its scrolling and buffer behavior, its almost impossible to get right. I wasn't planning on sharing my project on HN until I've written up more documentation, but I'm actually working on exactly this problem. https://github.com/aaronjanse/i3-tmux So far I…
How is the colour support better?
I don't have zsh setup on the OS I'm running currently, but a simple example is that the light-grey autocomplete text from zsh/oh-my-zsh shows up on i3-tmux but not tmux (at least at the time of writing).
I honestly don't remember the exact details, and maybe it's now fixed.
Re: Eternal Terminal
#53It is down for me, I wonder if .dev domain is filtered for me? Anyone has issues accesing this?
If you ping eternalterminal.dev, does it go straight to localhost? If so, it's probably your own computer that's redirecting .dev to localhost.
Re: Eternal Terminal
#54This is a good landing page. Every open source project should have something like this.
And this is how you create useful software. Looking for something to work? Try solving a problem you have. This is a so basic feature and so useful too.
Re: Eternal Terminal
#55My first question I couldn't find answered easily is "How does it work", e.g. "How does it maintain the connection?
The answer so far is that it does require you to install ET on the server too, along with the client. And then I searched github for "multiplex" thinking maybe it uses TCP multiplexing. And found a branch named "multiplex". Then I realized the Linux feature I was thinking of is actually called TCP Multipath, searched for it and no go. So I can only say that it _seems_ that it is _not_ using TCP Multipath for maintaining the connection over multiple connection drops.
Would love a more technical "How" here.
Re: Eternal Terminal
#56My first question I couldn't find answered easily is "How does it work", e.g. "How does it maintain the connection? The answer so far is that it does require you to install ET on the server too, along with the client. And then I searched github for "multiplex" thinking maybe it uses TCP multiplexing. And found a branch named "multiplex". Then I realized the Linux feature I was thinking of is actually called TCP Multi…
Here it is, I didn't see it hanging out at the top right of the page (#ux test).
Re: Eternal Terminal
#57I am probably missing the point here, but how is this different than connecting via ssh and doing tmux attach?
Re: Eternal Terminal
#58Earlier quoted context omitted.
How is the colour support better?
I don't have zsh setup on the OS I'm running currently, but a simple example is that the light-grey autocomplete text from zsh/oh-my-zsh shows up on i3-tmux but not tmux (at least at the time of writing). I honestly don't remember the exact details, and maybe it's now fixed.
Most likely you are using the wrong TERM so tmux doesn't have the correct information about what colours your terminal supports.
Re: Eternal Terminal
#59Earlier quoted context omitted.
Actually, I found the homepage (landing page) not so great, and came here to the comments, in the hope to get some more information. Specifically, I use Mosh, and I would like to know, is this the same thing? If yes, how is it different? What are advantages/disadvantages? I would have wanted a more detailed comparison. The name is also a bit confusing; just from the name, I thought this might be a terminal emulator.…
My understanding is: Mosh can't scroll because it doesn't send you the full output of the terminal. It only sends you the current "window" (visible terminal contents) at the current time. ET sends you everything. So if a program suddenly outputs a massive number of lines, mosh will discard the beginning and only send you the visible end of the output. ET will send you everything - which might bog down slow connection…
I'd like something cleverer than that.
Act like mosh but use spare time/capacity to send the historical buffer too.
That way you get the best of both worlds.
Re: Eternal Terminal
#60For someone wondering "how is this different from screen?/ what problem does it solve?", this article was actually quite nice: https://medium.com/@grassfedcode/what-could-be-better-than-s...
This article didn't help with screen, but it convinced me that eternal terminal isn't what I want because I often leverage mosh over poor connections and I generally use tmux anyway.