Hello,
First of all, thanks for this really neat package. I'm using it daily and enjoying it.
I would like to propose a customization toggle for the behavior of respawning dead shell buffers.
I can submit a PR if you want, but would first like to propose the idea.
Current behavior
When the comint process in interactive shell buffer dies, shx makes it come back to life whihc is really handy.
This is handled by the first cond of shx-send-input
.
The only problem is that when the shell was remote, it will respawn in a local shell instead.
Expected behavior
I understand that some users might want this behavior by default, but what I would personally expect is to have it respawned at the previous location (i.e. on the remote server).
I work daily with lots of remote server connections and have helper functions for connecting to them and naming the shell buffers according to the remote location.
I guess a var could be defined to let the user choose the behavior (respawn local or keep old location).
In the meantime, I have overridden shx-send-input
in my own config to keep my sanity.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4