Shell as an engine for TUI or GUI https://github.com/oilshell/oil/issues/738
That came out of a discussion with someone doing a really ambitious overhaul of terminals and display servers (linked in the issue).
I believe you could do some interesting things UI-wise with a shell that doesn't run in a terminal itself. The subprocesses would require a terminal, but the shell wouldn't. For example I've heard the suggestion to always keep the prompt at the top of the screen from a few people. That seems like it would be straightforward in an HTML UI, but it probably requires some cooperation from the shell itself.
Provide APIs to allow users to write their own line editor / interactive interface https://github.com/oilshell/oil/issues/663
This is a more Emacs-like architecture for a shell, with the interface being written in a high-level language rather than C/C++. That came out of running parts of ble.sh, which is an interactive shell written in bash !! (I believe it's the biggest bash program in the world, in both number of lines and sophistication)
If you have any ideas or suggestions, I'm interested. In the interest of time, I'm cutting out the interactive parts of the project and making it more like a library that other people can build shell UIs on top of.
I collected these links awhile ago but haven't done anything with them, there is some overlap:
https://github.com/oilshell/oil/wiki/Interactive-Shell
More shells here: https://github.com/oilshell/oil/wiki/ExternalResources
I guess you mean each command not affecting the very next command that follows?
I try and remember to have that installed on the heavy-interactive-use servers I admin for when users have an "oshi-" moment because they forgot to start something under screen.
zle-line-init() if [[ $CONTEXT = start ]] LBUFFER=$zle_prefix$LBUFFER
zle -N zle-line-init
mkdir $HOME/dtaches
zle_prefix='dtach -A $(mktemp -d $HOME/dtaches/XXXXX)/sock '