Interesting shellSat, Feb 25, 2012
Finally here is my last compilation about shell environment variables.
If this is set, keeps a directory list separated by ‘:’ and every time that you type the command “cd DIR” it searches for the directory in the above list, even if your current directory is not the right one. Let’s see an example, I define the directory holding all my git repositories, if I try to make cd repo from any part on the system, even if I not in the right place, I will get there:
export CDPATH="~/mygits" devadm@testing$(~)ls mygits blog scripts org-mode cv devadm@testing$(/usr/share/doc) cd blog devadm@testing$(~/mygits/blog)
In my opinion is useful to keep just one directory or probably up to two, more than this, it could get messy.
If you want to narrow down the ouput when performing filename completion, this is without a doubt your shell env. When set, it ignores suffixes while performing filename completion.
devadm@testing$(~)export FIGIGNORE="#:.o:~" devadm@testing$(~/application)ls file* file1.o file2.o file1 file1 file~ devadm@testing$(~)ls [TAB] [TAB] file1 file2
I mentioned this shell env because it was curious to me. I guess I have never found any case where I had to use such a thing, but that does not mean it wouldn’t be useful to somebody else.
It can be set to ignorespace , and it does not record words starting with empty space. On the other hand I do not like to have duplicated lines, ingnoredups does not repeat entries in the history. Finally, I like to join both options so I use ignoreboth instead.
It holds the path to a file containing a list of hosts in the same format as /etc/hosts , if it is set, tries to complete the hostname with one of the entries on the file. Otherwiese will look for /etc/hosts.
It could be pretty useful if you want to keep a personal file with your hosts.
The only problem I see here, if I you want to access hosts defined in /etc/hosts. You could make a script that checks if there is a new entry in the /etc/hosts and then appends the last entries to your personal list. Once again, this is only an idea I came up with, but actually I did not follow through.
If set, bash uses its value as the name of a directory in which creates temporary files. With this option I can set my personal temp directory.
Sets a timeout and affects to read or select builtin commands, when not input is given. An interesting case is if you set this to your current shell. After N seconds without providing any input it will kill your shell, so keep this in mind.
#!/bin/bash # Sets to 3 seconds timeout TMOUT="3" printf 'Could you please give me an absolute path ?' read -r -s -n10 absolute_path [ -z name ] && printf 'Your path is : %s\n' $absolute_path
Well, the last posts were focused on bash shell environment because I was digging into the man bash and I found quite interesting things I did not know, I hope some of them were useful for you as well.