This would make it much easier to script actions that depend on output that hadn't necessarily been anticipated or intentionally captured to a variable, but has a predictable pattern (for me this is often unexpected build failures for nix builds, which end in something like for access to the full logs, run 'nix log /nix/store/asdfasfoiwjef-foo/woeifjoxidfjj-bar', where the /nix/store path is not predictable; being able to dump screen output to stdout would allow me to sed/grep/awk my way to running that nix log without having to manually copy and paste the exact path).
Thanks for your work on zellij -- it's been fun and interesting learning to adapt my workflows!
I wanted to request the ability to dump-screen to stdout. At least on MacOS I can't find a simple way to do this:
This would make it much easier to script actions that depend on output that hadn't necessarily been anticipated or intentionally captured to a variable, but has a predictable pattern (for me this is often unexpected build failures for nix builds, which end in something like
for access to the full logs, run 'nix log /nix/store/asdfasfoiwjef-foo/woeifjoxidfjj-bar', where the/nix/storepath is not predictable; being able to dump screen output to stdout would allow me to sed/grep/awk my way to running thatnix logwithout having to manually copy and paste the exact path).Thanks for considering!