More About Angle Brackets in Bash

More About Angle Brackets in Bash - Printable Version

+- Sick Gaming (https://sickgaming.net)
+-- Forum: Computers (https://sickgaming.net/forum-86.html)
+--- Forum: Linux, BSD & Unix (https://sickgaming.net/forum-88.html)
+--- Thread: More About Angle Brackets in Bash (/thread-88454.html)

More About Angle Brackets in Bash - xSicKxBot - 01-30-2019

More About Angle Brackets in Bash

In the previous article, we introduced the subject of angle brackets (

Code:
< >

) and demonstrated some of their uses. Here, we’ll look at the topic from a few more angles. Let’s dive right in.

You can use

Code:
<

to trick a tool into believing the output of a command is data from a file.

Let’s say you are not sure your backup is complete, and you want to check that a certain directory contains all the files copied over from the original. You can try this:

Code:
diff <(ls /original/dir/) <(ls /backup/dir/)

Code:
diff

is a tool that typically compares two text files line by line, looking for differences. Here it gets the output from two

Code:
ls

commands and treats them as if coming from a file and compares them as such.

Note that there is no space between the

Code:
<

and the

Code:
(...)

.

Running that on the original and backup of a directory where I save pretty pictures, I get:

Code:
diff <(ls /My/Pictures/) <(ls /My/backup/Pictures/) 5d4 < Dv7bIIeUUAAD1Fc.jpg:large.jpg

The

Code:
<

in the output is telling me that there is file (Dv7bIIeUUAAD1Fc.jpg:large.jpg) on the left side of the comparison (in /My/Pictures) that is not on the right side of the comparison (in /My/backup/Pictures), which means copying over has failed for some reason. If

Code:
diff

didn’t cough up any output, it would mean that the list of files were the same.

So, you may be wondering, if you can take the output of a command or command line, make it look like the contents of a file, and feed it to an instruction that is expecting a file, that means that in the sorting by favorite actor example from above, you could’ve done away with the intermediate file and just piped the output from the loop into

Code:
sort

.

In short, yep! The line:

Code:
sort -r <(while read -r name surname films;do echo $films $name $surname ; done < CBactors)

does the trick nicely.

Here string! Good string!

There is one more case for redirecting data using angle brackets (or arrows, or whatever you want to call them).

You may be familiar with the practice of passing variables to commands using

Code:
echo

and a pipe (

Code:
|

). Say you want to convert a variable containing a string to uppercase characters because… I don’t know… YOU LIKE SHOUTING A LOT. You could do this:

Code:
myvar="Hello World" echo $myvar | tr '[:lower:]' '[:upper:]' HELLO WORLD

The

Code:
tr

command translates strings to different formats. In the example above, you are telling

Code:
tr

to change all the lowercase characters that come along in the string to uppercase characters.

It is important to know that you are not passing on the variable, but only its contents, that is, the string “Hello World“. This is called the here string, as in “it is here, in this context, that we know what string we are dealing with“. But there is shorter, clearer, and all round better way of delivering here strings to commands. Using

Code:
tr '[:lower:]' '[:upper:]' <<< $myvar

does the same thing with no need to use echo or a pipe. It also uses angle brackets, which is the whole obsessive point of this article.

Conclusion

Again, Bash proves to give you lots of options with very little. I mean, who would’ve thunk that you could do so much with two simple characters like

Code:
<

and

Code:
>

?

The thing is we aren’t done. There are plenty of more characters that bring meaning to chains of Bash instructions. Without some background, they can make shell commands look like gibberish. Hopefully, post by post, we can help you decipher them. Until next time!