{"id":451,"date":"2020-04-22T16:05:17","date_gmt":"2020-04-22T21:05:17","guid":{"rendered":"https:\/\/cdrhdev.unl.edu\/log\/?p=451"},"modified":"2020-04-22T16:49:11","modified_gmt":"2020-04-22T21:49:11","slug":"plant-a-tree-in-the-command-line","status":"publish","type":"post","link":"https:\/\/cdrhdev.unl.edu\/log\/2020\/plant-a-tree-in-the-command-line\/","title":{"rendered":"Plant a Tree in the Command Line"},"content":{"rendered":"

Happy 50th Anniversary of Earth Day!<\/p>\n

Not all of us can plant a tree or do other restorative work for Earth Day, and in the face of large-scale problems to solve we don’t always feel like the small things we do to help (reducing the amount of water or electricity we use) matter. But the small things do help. For me, this recently was highlighted in another part of my life in the form of a handy little command line tool.<\/p>\n

I was feeling that having to enter cd<\/code> (change directory) and ls<\/code> (list directory contents) commands over and over to examine the contents of the file system on the command line was an inefficient way to get a good picture of the files and directories. This is more frequently an issue when I download software to install or am getting familiar with files for a project already under way. What kinds of files are there, and how are they organized?<\/p>\n

I performed some simple web searches and found tree<\/code><\/a>. It outputs a recursive directory listing in an easy-to-read tree format. It also provides a variety of options to filter what will be displayed and whether extra information beyond the file name is shown.<\/p>\n

\"tree
Figure 1<\/figcaption><\/figure>\n

Install tree<\/code><\/h2>\n

tree<\/code> is available on a large variety of operating systems. Linux, Mac, and even Windows with cygwin. I’ll just share the simplest ones for quick reference.<\/p>\n

Fedora \/ CentOS \/ Red Hat \/ Other YUM-based Systems<\/strong><\/p>\n

sudo yum install tree<\/code><\/p>\n

Debian \/ Ubuntu \/ Other APT-based Systems<\/strong><\/p>\n

sudo apt-get install tree<\/code><\/p>\n

Mac OS with Brew<\/strong><\/p>\n

brew install tree<\/code><\/p>\n

Example Usage<\/h2>\n

Running tree<\/code> with no arguments will recursively list every single file and directory from the current directory. This is usually far too much information to be useful for a quick glance to get the big picture of file system organization. So here are a couple options to help narrow output to something more useful:<\/p>\n

Colorize Output<\/h3>\n

tree -C<\/code><\/p>\n

This was used in Figure 1. Without this option, tree<\/code> will display all files and directories with the same color. This option may not be as helpful for individuals with color-blindness or limited sight, but customizing the LS_COLORS<\/code> environment variable which controls the colorization may help there. I personally use Dark Solarized colors via dircolors-solarized<\/a>. David Newcomb has a blog post digging further into configuring LS_COLORS<\/a>.<\/p>\n

To always get colorized output without needing to specify the -C<\/code> option every time, create an alias to apply it for you with alias 'tree'='tree -C'<\/code>. Now calling tree<\/code> from the command line will include the colorization option automatically. Creating the alias this way is temporary, but you can make this persist across all future terminals by adding it to your Bash startup script(s)<\/a>.<\/p>\n

Limit Recursion Depth<\/h3>\n

tree -L 3<\/code><\/p>\n

This limits the depth of directories tree<\/code> will traverse for listing files and directories. This limits output to more of a surface-level picture of a directory’s contents.<\/p>\n

\"tree
Figure 2<\/figcaption><\/figure>\n

Only Display Directories<\/h3>\n

tree -d<\/code><\/p>\n

This limits tree<\/code> to only list directories, for a more structural examination of a directory’s contents.<\/p>\n

\"tree
Figure 3<\/figcaption><\/figure>\n

List Only or Ignore Files Matching a Pattern<\/h3>\n

tree -P *.png<\/code><\/p>\n

This option will search the files and only list files which match a pattern (which follows the Bash globbing pattern syntax) and the intermediary parent directories of those files.<\/p>\n

\"tree
Figure 4<\/figcaption><\/figure>\n

tree -I *.png<\/code><\/p>\n

This option will display the inverse by ignoring all files which match the pattern entered.<\/p>\n

\"tree
Figure 5<\/figcaption><\/figure>\n

Ignore Directories with Lots of Files<\/h3>\n

tree --filelimit 4<\/code><\/p>\n

This will stop tree<\/code> from recursing down into directories which contain more than the specified total number of files and directories at the next level down. This is another way to limit things to a more surface-level view and shorten the length of output.<\/p>\n

\"tree
Figure 6<\/figcaption><\/figure>\n

Show Permissions<\/h3>\n

tree -p<\/code><\/p>\n

This shows permissions alongside the files and directories.<\/p>\n

\"tree
Figure 7<\/figcaption><\/figure>\n

Display Another Directory<\/h3>\n

tree -CI *.log -L 2 \/var\/local\/www\/data<\/code><\/p>\n

This command is combining a few of our examples, but the new part is just specifying a different directory at the end. This can be used to help minimize the repeated cd<\/code> command usage I mentioned earlier.<\/p>\n

\"tree
Figure 8<\/figcaption><\/figure>\n

Reduce Usage<\/h2>\n

Much like tree<\/code> has helped me reduce my usage of the cd<\/code> and ls<\/code> commands, I hope for Earth Day you will take some time to reflect on your own habits and reduce usage of resources, whether it be disposable products as opposed to reusable ones, containers which can’t be recycled, water in the shower, gasoline for driving (take it easy on the accelerator), gas for heating, or electricity for lighting and appliances.<\/p>\n

I hope you found this helpful and have a healthy day!<\/p>\n","protected":false},"excerpt":{"rendered":"

Happy 50th Anniversary of Earth Day! Not all of us can plant a tree or do other restorative work for Earth Day, and in the face of large-scale problems to solve we don’t always feel like the small things we do to help (reducing the amount of water or electricity we use) matter. But the…<\/p>\n Read More<\/span> Plant a Tree in the Command Line<\/span><\/a>","protected":false},"author":3,"featured_media":455,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"Layout":"","footnotes":""},"categories":[40],"tags":[64,63],"class_list":["entry","author-techgique","post-451","post","type-post","status-publish","format-standard","has-post-thumbnail","category-utilities","tag-bash","tag-command-line"],"_links":{"self":[{"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/posts\/451","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/comments?post=451"}],"version-history":[{"count":11,"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/posts\/451\/revisions"}],"predecessor-version":[{"id":472,"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/posts\/451\/revisions\/472"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/media\/455"}],"wp:attachment":[{"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/media?parent=451"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/categories?post=451"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cdrhdev.unl.edu\/log\/wp-json\/wp\/v2\/tags?post=451"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}