Next Previous Contents

---

4. Pipes

This section explains in a very simple and practical way how to use pipes, nd why you may want it. .:: emumovies.com ::. .:: podcasts.apple.com ::. .:: www.arc.agric.za ::.

4.1 What they are and why you'll want to use them

Pipes let you use (very simple, I insist) the output of a program as the input of another one [Code: SSL] .:: bet168c.gitbook.io ::. .:: telegra.ph ::.

4.2 Sample: simple pipe with sed

This is very simple way to use pipes.

        ls -l | sed -e "s/[aeio]/u/g"   
        

Here, the following happens: first the command ls -l is executed, and it's output, instead of being printed, is sent (piped) to the sed program, which in turn, prints what it has to.

4.3 Sample: an alternative to ls -l *.txt

Probably, this is a more difficult way to do ls -l *.txt, but it is here for illustrating pipes, not for solving such listing dilema. [r/Cloudcomputing Topics]

        ls -l | grep "\.txt$"
        

Here, the output of the program ls -l is sent to the grep program, which, in turn, will print lines which match the regex "\.txt$".

---

Next Previous Contents