{"id":90700,"date":"2019-03-26T14:00:50","date_gmt":"2019-03-26T14:00:50","guid":{"rendered":"http:\/\/www.sickgaming.net\/blog\/2019\/03\/26\/using-square-brackets-in-bash-part-1\/"},"modified":"2019-03-26T14:00:50","modified_gmt":"2019-03-26T14:00:50","slug":"using-square-brackets-in-bash-part-1","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2019\/03\/26\/using-square-brackets-in-bash-part-1\/","title":{"rendered":"Using Square Brackets in Bash: Part 1"},"content":{"rendered":"
<\/div>\n

After taking a look at how curly braces ({}<\/code>) work on the command line<\/a>, now it\u2019s time to tackle brackets ([]<\/code>) and see how they are used in different contexts.<\/p>\n

Globbing<\/h3>\n

The first and easiest use of square brackets is in globbing<\/em>. You have probably used globbing before without knowing it. Think of all the times you have listed files of a certain type, say, you wanted to list JPEGs, but not PNGs:<\/p>\n

\nls *.jpg<\/pre>\n
Using wildcards to get all the results that fit a certain pattern is precisely what we call globbing.<\/p>\n
In the example above, the asterisk means “zero or more characters<\/i>“. There is another globbing wildcard, ?<\/code>, which means “exactly one character<\/i>“, so, while<\/p>\n
 ls d*k*\n<\/pre>\n
will list files called darkly<\/i> and ducky<\/i> (and dark<\/i> and duck<\/i> — remember *<\/code> can also be zero characters),<\/p>\n
 ls d*k? <\/pre>\n
will not list darkly<\/i> (or dark<\/i> or duck<\/i>), but it will list ducky<\/i>.<\/p>\n
Square brackets are used in globbing for sets of characters. To see what this means, make directory in which to carry out tests, cd<\/code> into it and create a bunch of files like this:<\/p>\n
 touch file0{0..9}{0..9} <\/pre>\n
(If you don’t know why that works, take a look at the last installment that explains curly braces {}<\/code><\/a>).<\/p>\n
This will create files file000<\/i>, file001<\/i>, file002<\/i>, etc., through file097<\/i>, file098<\/i> and file099<\/i>.<\/p>\n
Then, to list the files in the 70s and 80s, you can do this:<\/p>\n
 ls file0[78]? <\/pre>\n
To list file022<\/i>, file027<\/i>, file028<\/i>, file052<\/i>, file057<\/i>, file058<\/i>, file092<\/i>, file097<\/i>, and file98<\/i> you can do this:<\/p>\n
 ls file0[259][278] <\/pre>\n
Of course, you can use globbing (and square brackets for sets) for more than just ls<\/code>. You can use globbing with any other tool for listing, removing, moving, or copying files, although the last two may require a bit of lateral thinking.<\/p>\n
Let’s say you want to create duplicates of files file010<\/i> through file029<\/i> and call the copies archive010<\/i>, archive011<\/i>, archive012<\/i>, etc..<\/p>\n
You can’t do:<\/p>\n
 cp file0[12]? archive0[12]? <\/pre>\n
Because globbing is for matching against existing files and directories and the archive…<\/i> files don’t exist yet.<\/p>\n
Doing this:<\/p>\n
 cp file0[12]? archive0[1..2][0..9] <\/pre>\n
won’t work either, because cp<\/code> doesn’t let you copy many files to other many new files. Copying many files only works if you are copying them to a directory, so this:<\/p>\n
 mkdir archive cp file0[12]? archive <\/pre>\n
would work, but it would copy the files, using their same names, into a directory called archive\/<\/i>. This is not what you set out to do.<\/p>\n
However, if you look back at the article on curly braces ({}<\/code>)<\/a>, you will remember how you can use %<\/code> to lop off the end of a string contained in a variable.<\/p>\n
Of course, there is a way you can also lop of the beginning of string contained in a variable. Instead of %<\/code>, you use #<\/code>.<\/p>\n
For practice, you can try this:<\/p>\n
 myvar=\"Hello World\" echo Goodbye Cruel ${myvar#Hello} <\/pre>\n
It prints “Goodbye Cruel World<\/i>” because #Hello<\/code> gets rid of the Hello<\/i> part at the beginning of the string stored in myvar<\/code>.<\/p>\n
You can use this feature alongside your globbing tools to make your archive<\/i> duplicates:<\/p>\n
 for i in file0[12]?;\\ do\\ cp $i archive${i#file};\\ done <\/pre>\n
The first line tells the Bash interpreter that you want to loop through all the files that contain the string file0<\/i> followed by the digits 1<\/i> or 2<\/i>, and then one other character, which can be anything. The second line do<\/code> indicates that what follows is the instruction or list of instructions you want the interpreter to loop through.<\/p>\n
Line 3 is where the actually copying happens, and you use the contents of the loop variable i<\/code><\/em> <\/em>twice: First, straight out, as the first parameter of the cp<\/code> command, and then you add archive<\/i> to its contents, while at the same time cutting of file<\/i>. So, if i<\/code><\/em> contains, say, file019<\/i>…<\/p>\n
 \"archive\" + \"file019\" - \"file\" = \"archive019\" <\/pre>\n
the cp<\/code> line is expanded to this:<\/p>\n
 cp file019 archive019 <\/pre>\n
Finally, notice how you can use the backslash \\<\/code> to split a chain of commands over several lines for clarity.<\/p>\n
In part two, we\u2019ll look at more ways to use square brackets. Stay tuned.<\/p>\n","protected":false},"excerpt":{"rendered":"
After taking a look at how curly braces ({}) work on the command line, now it\u2019s time to tackle brackets ([]) and see how they are used in different contexts. Globbing The first and easiest use of square brackets is in globbing. You have probably used globbing before without knowing it. Think of all the times […]<\/p>\n","protected":false},"author":2,"featured_media":90701,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[40],"tags":[],"class_list":["post-90700","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux-freebsd-unix"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/90700","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=90700"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/90700\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media\/90701"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=90700"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=90700"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=90700"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}