The search path is a list of directories in which the operating system scans for programs. Its purpose is to allow quick access to common programs and system utilities without the necessity of typing a full pathname or changing to the right directory to start an application.
\n
\nBack in the text mode days, the search path was extremely helpful. It remains so today in the terminal window: Directories full of common programs are listed on the path. When you type a command, the operating system searches each directory on the path for a matching program file.<\/p>\n
Various methods exist to display the search path, but you can write a quick utility in C that displays each directory on a line by itself. To do so, you must examine the system’s environment and look for the PATH variable. I demonstrated such a program back in 2013’s blog post<\/a> on the environment:<\/p>\n With just a few modifications, you can dump out the directory list by scanning through the string returned ( In Windows, the path separator character is For Unix, the path separator character is Here’s the code:<\/p>\n Comment out Line 4 or 5, depending on the OS.<\/p>\n Character pointer The while<\/em> loop at Line 14 steps through the string one character at a time. If the character matches the Line 20 increments variable Here’s sample output from my Mac:<\/p>\n In Windows, the list is much longer. It’s been tradition in Windows (since the days of MS-DOS) to stack directories in the path for each program installed. Some applications are getting better at avoiding this noisome tradition, but you still find plenty that insist upon putting their own directories on the path.<\/p>\n In my Mac’s path, you see the directory Here’s a handy utility that displays directories specified by the operating system in which to find executable (program) files. Continue reading \r\n#include <stdio.h>\r\n#include <stdlib.h>\r\n\r\nint main()\r\n{\r\n char *searchpath;\r\n\r\n searchpath = getenv(\"PATH\");\r\n printf(\"The search path is '%s'\\n\",searchpath);\r\n return(0);\r\n}<\/pre>\nsearchpath<\/code>) and replacing the path separator character with a newline.<\/p>\n;<\/code>, the semicolon.<\/p>\n:<\/code>, the colon.<\/p>\n\r\n#include <stdio.h>\r\n#include <stdlib.h>\r\n\r\n#define SEPARATOR ';'\r\n#define SEPARATOR ':'\r\n\r\nint main()\r\n{\r\n char *searchpath,*s;\r\n\r\n searchpath = getenv(\"PATH\");\r\n s = searchpath;\r\n\r\n while(*s)\r\n {\r\n if( *s == SEPARATOR)\r\n putchar('\\n');\r\n else\r\n putchar(*s);\r\n s++;\r\n }\r\n putchar('\\n');\r\n\r\n return(0);\r\n}<\/pre>\ns<\/code> is initialized to the base of the string returned at Line 12.<\/p>\nSEPARATOR<\/code>, a newline is output. Otherwise, the character found is output.<\/p>\ns<\/code> to keep moving through the string.<\/p>\n\/usr\/local\/bin
\n\/usr\/bin
\n\/bin
\n\/usr\/sbin
\n\/sbin
\n\/Users\/dang\/bin<\/code><\/p>\n\/Users\/dang\/bin<\/code>. Into this directory I place all my command line utilities, most of which are written in C but with a few in Bash shell script and some in Perl. Having this personal bin<\/code> directory allows me to use my utilities in any directory when I’m working in a terminal window — which is quite often. I find the C language quite practical for writing such short, useful command line utilities, as did Unix titans Ken Thompson, Brian Kernighan, and Dennis Ritchie. I hope you do as well.<\/p>\n","protected":false},"excerpt":{"rendered":"