4 ms·

Maybe I'm just old and grumpy, but what do you gain by this compared to just building up your pipe directly in the shell? Not having to hit enter once in a whil

Maybe I'm just old and grumpy, but what do you gain by this compared to just building up your pipe directly in the shell? Not having to hit enter once in a while?

jolmg 6y ago
You still have to press Enter. I'm with you. I can't see myself preferring this over using my shell's interactive prompt, history, and a use of head/less at the end. Thanks to the author and OP for sharing and it's good for other people if they find this useful, though. EDIT: Maybe I could find this useful when the command that provides `up`'s input is not something that can be repeated for the same input. But even then, you can put it in the background with its output redirected to a file, then make the command that you would build inside `up` from a pipe like `tail -fn+1 bg-job.out | cmd`.
akavel 6y ago
Not much, really. Yet somehow those little things add up to something... faster :) Basically "just": - not having to append `| head -n $ROWS` or something similar on every command (yet having the view as-if-you-typed-it, but at the same time being able to scroll down further through the results; and having them visible as you continue tweaking, unlike `less` which you have to quit to tweak the pipeline), - not having to press up-arrow-key, then alt-b / alt-f to a position in the pipeline you want to tweak after every Enter (e.g. just before the `| head...`, but sometimes a bit more back), - sometimes also not having to dump the initial input from a command into a file, and to wait until it's finished, but being able to immediately start filtering even while the input is still being generated. Once I just had those ideas, I felt pain every time I repeated the dance, enough that it made me push on up even when I was super tired of working on it. The pain of not having it when I know it could exist was even bigger.

Maybe I'm just old and grumpy, but what do you gain by this compared to just building up your pipe directly in the shell? Not having to hit enter once in a while?

jolmg 6y ago

You still have to press Enter. I'm with you. I can't see myself preferring this over using my shell's interactive prompt, history, and a use of head/less at the end. Thanks to the author and OP for sharing and it's good for other people if they find this useful, though. EDIT: Maybe I could find this useful when the command that provides `up`'s input is not something that can be repeated for the same input. But even then, you can put it in the background with its output redirected to a file, then make the command that you would build inside `up` from a pipe like `tail -fn+1 bg-job.out | cmd`.

akavel 6y ago

Not much, really. Yet somehow those little things add up to something... faster :) Basically "just": - not having to append `| head -n $ROWS` or something similar on every command (yet having the view as-if-you-typed-it, but at the same time being able to scroll down further through the results; and having them visible as you continue tweaking, unlike `less` which you have to quit to tweak the pipeline), - not having to press up-arrow-key, then alt-b / alt-f to a position in the pipeline you want to tweak after every Enter (e.g. just before the `| head...`, but sometimes a bit more back), - sometimes also not having to dump the initial input from a command into a file, and to wait until it's finished, but being able to immediately start filtering even while the input is still being generated. Once I just had those ideas, I felt pain every time I repeated the dance, enough that it made me push on up even when I was super tired of working on it. The pain of not having it when I know it could exist was even bigger.