transmission VS dtache

Very nice feature that one. Its RPC allows for other interfaces for control, it's great.

It'll shrink if you only use it for programming, but if you start using it for file management, email, NNTP, music, torrenting, etc, then individual sections might shrink as your understanding grows and you refine them, but more will be added as new use-cases are covered.

For eshell and other commands yeah that works but that's the usual fallback, not a first-class Emacs UI like transmission.el (which doesn't require super-user shenanigans since its RPC supports authentication and can be reverse-forwarded with SSH).

It also has an Emacs control interface, which is nice.

I wouldn't do it simply because there are some things for which it doesn't work best such as using tmux over it and I haven't yet bothered to read & setup dtache which would solve that problem.

Another thing is why people may want to see the whole 10Mb compilation log in realtime? Redirect it to a file, M-x grep the things you need, and you are perfectly fine. There's also https://gitlab.com/niklaseklund/dtache

GNU Screen, tmux and dtach (with convenient Emacs interface) all serve to limit that problem.

Have a look at https://gitlab.com/niklaseklund/dtache

Here is a short blog post illustrating how dtache, the package for detached shell commands https://gitlab.com/niklaseklund/dtache, can be integrated with vterm.

Regarding 4), that's what got me into developing dtache https://gitlab.com/niklaseklund/dtache. Could be an alternative if you want to avoid leaving Emacs :)

There is a version 0.4 out for the **dtache** package. The short description of the package is that it provides the possibility to run commands that are detached from Emacs. To read more see the README here https://gitlab.com/niklaseklund/dtache. The major changes compared to the last release is:

The other day I merged an extension to integrate dtache with consult. The dtache is the package for detachable shell commands https://gitlab.com/niklaseklund/dtache. The functionality is opt in, and provided through the dtache-consult.el.

You can read more about, and see some examples of dtache-eshell in action at https://niklaseklund.gitlab.io/blog/posts/dtache_eshell/, and if you are looking for the source code you will find it here https://gitlab.com/niklaseklund/dtache :)