Feature Request: syntax for piping data into stdin of tasks

[edwloef]

E.g. {{selection}} > sort, which would pipe the current selection into sort's stdin. I opted for one > instead of two to make it mirror the bash output redirect operator (vs the output append operator), but I'm not entirely sure that's the best idea since it might cause ambiguity or unexpected behavior if the selection holds a command that's meant to be run?

[neurocyte]

since it might cause ambiguity or unexpected behavior if the selection holds a command that's meant to be run?

{{selection}}>... will be special cased and not just forwarded to bash, as that would have the same maximum command line issues as just using echo {{selection}} | sort. The part after the > symbol can however be a shell call.