WINTEXT(1)

okay bestie, welcome to WINTEXT(1) from the General Commands Manual — the page about grabbing text from your current window and pulling commands out of it. it's giving terminal archaeology and honestly? obsessed. 💅✨

✨ NAME ✨

wintext, ", and "" — access text in the current window. periodt. 💖

🎀 SYNOPSIS 🎀

The shape of it, exactly:

wintext
" [ prefix ]
"" [ prefix ]

💅 DESCRIPTION 💅

wintext prints the text of the current win (see acme(1), 9term(1), or (Unix's) tmux(1)) window to standard output. iconic behavior, no notes. 💖

" searches the window text for commands typed with a particular prefix and prints them, indented, to standard output. Prefix is a regular expression that is matched against the beginning of the command-line. If prefix is omitted, " prints the last command executed. 🕵️‍♀️

"" takes the same optional prefix, prints the last command that " would print, and then executes it by piping it into rc(1). main character energy: it doesn't just look, it runs. 🔥

Both " and "" identify commands in the window text by looking for lines beginning with a shell prompt. Prompts are assumed to be an unindented sequence of non-whitespace characters followed by one of the characters %, ;, $, or #. iykyk. 🦋

🌈 EXAMPLES 🌈

Print the ls(1) and lc commands executed in this window:

% " 'l[sc]'
    % ls -l /tmp/qq*
    # ls -lrt /etc
    % lc r*
%

Execute the most recent lc command again:

% "" lc
    % lc r*
ramfs   rc      read    rio     rm
%

🦋 SEE ALSO 🦋

9term(1), acme(1) — go give them a lil visit. 🫶

🍓 SOURCE 🍓

/bin

💀 BUGS 💀

real talk: " and "" are hard to type in shells other than rc(1). not me fighting my keyboard in literally any other shell 😭💀

That's the whole WINTEXT(1) page, bestie. Footer says WINTEXT(1) again; no version or date was printed, and the source listed above is /bin. slay, read the manual, and go grab that window text 🫶✨