4 ms·

Here is my quick wish list of features I think I would use at least weekly if my terminal included them. - jump to previous commands. You just ran a command t

Here is my quick wish list of features I think I would use at least weekly if my terminal included them. - jump to previous commands. You just ran a command that printed a few pages, you want to scan from the first line. You have to scroll up and find the last prompt, where you typed the command. Why isn't there a shortcut for this? - collapse previous outputs (stderr / stdout / both) Hmmm, were there any warnings in the build I just ran? Anything on stderr? Let me toggle stdout / stderr after the command has been run. - connect a pipe to a previously run command You run a computation that takes a minute and produces a few pages of output. You realize you want the output sorted. So you run it again. You could pipe to sort, or if you piped to a file you could cat the file next time you needed the output. But why can't you re-use the output that is there in the terminals scrollback buffer?

sigjuice 9y ago
Emacs shell-mode does the first one. The other two should be trivial for someone moderately proficient in elisp.
gluggymug 9y ago
>- jump to previous commands. >You just ran a command that printed a few pages, you want to scan from the first line. I think tmux might get you there. You bind a key to enter copy-mode and backward search for your particular prompt. >- collapse previous outputs (stderr / stdout / both) > Let me toggle stdout / stderr after the command has been run. That sounds like a good one. >- connect a pipe to a previously run command >... But why can't you re-use the output that is there in the terminals scrollback buffer? Once again tmux could "save-buffer" to a file for you if you did that backwards search then copy to a paste buffer. Just bind another key.
eridius 9y ago
> You just ran a command that printed a few pages, you want to scan from the first line. You have to scroll up and find the last prompt, where you typed the command. Why isn't there a shortcut for this? macOS's Terminal.app has this. Key shortcuts can jump between prompts (or between marked lines if you want to press a key combo to mark arbitrary lines), and can also select all text to the previous/next prompt (so you can trivially copy the output of a command). > Hmmm, were there any warnings in the build I just ran? Anything on stderr? Let me toggle stdout / stderr after the command has been run. Potentially interesting, but I'm not sure if it can actually be done. Both stdout and stderr are connected to the pty; can the pty meaningfully distinguish which connection is stdout and which is stderr? Also, what happens if stdout and stderr get mixed in the same line? You can't really collapse that.

sigjuice 9y ago

Emacs shell-mode does the first one. The other two should be trivial for someone moderately proficient in elisp.

gluggymug 9y ago

>- jump to previous commands. >You just ran a command that printed a few pages, you want to scan from the first line. I think tmux might get you there. You bind a key to enter copy-mode and backward search for your particular prompt. >- collapse previous outputs (stderr / stdout / both) > Let me toggle stdout / stderr after the command has been run. That sounds like a good one. >- connect a pipe to a previously run command >... But why can't you re-use the output that is there in the terminals scrollback buffer? Once again tmux could "save-buffer" to a file for you if you did that backwards search then copy to a paste buffer. Just bind another key.

eridius 9y ago

> You just ran a command that printed a few pages, you want to scan from the first line. You have to scroll up and find the last prompt, where you typed the command. Why isn't there a shortcut for this? macOS's Terminal.app has this. Key shortcuts can jump between prompts (or between marked lines if you want to press a key combo to mark arbitrary lines), and can also select all text to the previous/next prompt (so you can trivially copy the output of a command). > Hmmm, were there any warnings in the build I just ran? Anything on stderr? Let me toggle stdout / stderr after the command has been run. Potentially interesting, but I'm not sure if it can actually be done. Both stdout and stderr are connected to the pty; can the pty meaningfully distinguish which connection is stdout and which is stderr? Also, what happens if stdout and stderr get mixed in the same line? You can't really collapse that.