NireBryce

reality is the battlefield

the first line goes in Cohost embeds

🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.


I wish there was cell-based terminal stuff. I want to be able to pin error/infomessages while going about the code, so I can say, see your 'what next' instructions while doing other things. I could open a new pane, but that loses my place -- I don't know any terminal emulators that can do 'new window at new location' outside maybe tmux.

but my ideal either being able to pin output, or being able to have program output mirrored on another screen, but terminal output omitted from it

and I don't know how possible that is


You must log in to comment.

in reply to @NireBryce's post:

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

but the ideal ideal for single-terminal workflows would be like... jupyter notebook, but without the ability to go back and edit already-run cells.

so like, imagine your scrollback was shell history but with stdout instead of stdin, and each entry is it's own chunk

if you're unfamiliar with Jupyter, here's the example from the website.

the top cell is input (I don't know how we could time travel something's state outside of maybe NixOS, so it wouldn't be editable) and the bottom cell is output

I don't think this is achievable rn, but that's what I reached for when I was like, wow I wish this was better at letting me do things I was asked to

ok but actually, its absurd that 'duplicate pane' behavior in at least windows terminal doesn't duplicate it over SSH, and while I understand some of that is on the protocol level and I should just use tmux, but it's not 2003 anymore and I'm not running irssi

okay, so like ideally, you'd be able to like, pin headers, like a spreadsheet does, it just keeps the top (or otherwise specified) few lines on screen while you scroll down the rest of the file? Or am I misunderstanding?

program output mirrored on another screen, but terminal output omitted from it

this almost sounds like something you could do with stream output fd's? like if you had stderr on a different screen and the program output what you wanted on stderr but stdout stays on the other terminal? it's a little involved haha but should be something you can script

love tech folks proudly proclaiming they don't need guis for terminals while those are things specifically designed to help you understand information more easily.

i personally gotta have a lil list of commands taped to my screen because every time i use it i just can't remember which command does what