whisperity
whisperity
There are several valid use cases in which the user's shell (inside a session) is not able to communicate directly with the server that is executing said session. The two...
> Idea was taken from [_abduco_](http://github.com/martanne/abduco/) This could perhaps even be extended with the client at connection time finding all monomux processes and instructing them to recreate their socket BEFORE...
Create a way to automatically execute bits 'n bobs of code at both session creation time, and at "sequence points" (such as prompt generations) within the session. Support at least...
Currently, if `XDG_RUNTIME_DIR` is not set and `TMPDIR` also is not set, the code immediately falls back to `/tmp/mnmx` even though we could at least add the user's name into...
1. Create and attach to session `A` 2. From within `A`, create and attach to session `B` 3. From within `B`, attach to session `A` Both clients' and the server's...
With in-line detachment getting implemented as part of #3, it should be noted that there are cases when detaching from a running session is **not safe** to the client's terminal...
E.g. in the interactive session selector, if the user just presses Return, the read keeps on reading from the next line which is visually unappealing.
Instead of having to call the `monomux` binary with a specific flag, the client itself should be able to send a request to detach, which would result in a graceful...
This would actually be a detach (#3) followed by re-running the already existing session-attachment logic, but without restarting the server.
For example, users might want to configure a project in a way that they would scrap the build artefacts to save space in case a many-project execution is done. There...