things like, as an arbitrary example,
==> Next steps:
- Run these three commands in your terminal to add Homebrew to your PATH:
echo '# Set PATH, MANPATH, etc., for Homebrew.' >> /home/elly/.profile
echo 'eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"' >> /home/elly/.profile
eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv)"
- Install Homebrew's dependencies if you have sudo access:
sudo apt-get install build-essential
For more information, see:
https://docs.brew.sh/Homebrew-on-Linux
- We recommend that you install GCC:
brew install gcc
- Run brew help to get started
- Further documentation:
https://docs.brew.sh
shouldn't be something you have to actively think about while editing things via SSH. I get that the current answer rn is 'have n > 1 panes' but that doesn't really solve the fact that there's no way to keep relevant information like, available.
Most of my ssh stuff is in one window because I'm doing it either in VSCode, or a quadrant of a 4k monitor (So, 1080p). I run something, get output, do things in response to that.
if I have to do two things I run two panes, but among other things I have like, a spatial sense that gets very confused if I'm in multiple terminals in multiple folders, and they will inevitably get that way.
tmux-repl comes close to this, but fails because I'd want it to be full output, and just have program output (but not shell output) be in the read only pane