Allow passing the command line as a command line argument to pipeline

[Aster89]

Since pipeline has no history (and that's, I think, intended/good/desired/good/verygood), sometimes it's a pain I have to reselect some text from the terminal just to put it in another session of pipeline.

Passing the command line to pipeline would be handy. Running pipeline on a command which is not doing what we want would be almost as easy as enclosing it in single quotes and prepending pipeline.

And it would have the advantage that that command is saved in the shell history (sure, if I modify the command once in pipeline, then there's no history for that).

Well, maybe another "sibling" improvement would be a key binding to exit pipeline and populate the command line with the last edited line.

Just some ideas. :)

[codekitchen]

👍 I started implementing the option to pass the initial command line in, but ran into some issues I can't recall, and never finished it. I'd like to get that in.

I don't think it's possible to exit and populate the command line, I could be wrong but pretty sure there's no general way to do that. Maybe specific terminals or shells support something.