github.com/lmorg/murex@v0.0.0-20240217211045-e081c89cd4ef/docs/parser/pipe-generic.md (about) 1 # `=>` Generic Pipe 2 3 > Pipes a reformatted STDOUT stream from the left hand command to STDIN of the right hand command 4 5 ## Description 6 7 This token behaves much like the `|` pipe would except it injects `format 8 generic` into the pipeline. The purpose of a formatted pipe is to support 9 piping out to external commands which don't support Murex data types. For 10 example they might expect arrays as lists rather than JSON objects). 11 12 13 14 ## Examples 15 16 ``` 17 » ja [Mon..Wed] => cat 18 Mon 19 Tue 20 Wed 21 ``` 22 23 The above is literally the same as typing: 24 25 ``` 26 » ja [Mon..Wed] -> format generic -> cat 27 Mon 28 Tue 29 Wed 30 ``` 31 32 To demonstrate how the previous pipeline might look without a formatted pipe: 33 34 ``` 35 » ja [Mon..Wed] -> cat 36 ["Mon","Tue","Wed"] 37 38 » ja [Mon..Wed] | cat 39 ["Mon","Tue","Wed"] 40 41 » ja [Mon..Wed] 42 [ 43 "Mon", 44 "Tue", 45 "Wed" 46 ] 47 ``` 48 49 ## See Also 50 51 * [Pipeline](../user-guide/pipeline.md): 52 Overview of what a "pipeline" is 53 * [`->` Arrow Pipe](../parser/pipe-arrow.md): 54 Pipes STDOUT from the left hand command to STDIN of the right hand command 55 * [`<read-named-pipe>`](../parser/namedpipe.md): 56 Reads from a Murex named pipe 57 * [`?` STDERR Pipe](../parser/pipe-err.md): 58 Pipes STDERR from the left hand command to STDIN of the right hand command (DEPRECATED) 59 * [`format`](../commands/format.md): 60 Reformat one data-type into another data-type 61 * [`ja` (mkarray)](../commands/ja.md): 62 A sophisticated yet simply way to build a JSON array 63 * [`|` POSIX Pipe](../parser/pipe-posix.md): 64 Pipes STDOUT from the left hand command to STDIN of the right hand command 65 66 <hr/> 67 68 This document was generated from [gen/parser/pipes_doc.yaml](https://github.com/lmorg/murex/blob/master/gen/parser/pipes_doc.yaml).