{"id":186,"date":"2018-10-19T12:00:00","date_gmt":"2018-10-19T04:00:00","guid":{"rendered":"https:\/\/yeslq.com\/201810186.html"},"modified":"2019-05-07T10:43:36","modified_gmt":"2019-05-07T02:43:36","slug":"the-linux-command-line-keyboard-inpu","status":"publish","type":"post","link":"https:\/\/yeslq.com\/?p=186","title":{"rendered":"The Linux Command Line—Keyboard Input And Arithmetic"},"content":{"rendered":"

\nThe Linux Command Line <\/a><\/i>by William Shotts<\/span><\/h1>\n
\n
<\/span><\/div>\n
\n<\/p>\n
\nUp to now, our scripts have not been interactive. That is, they did not require any input from the user. In this lesson, we will see how your scripts can ask questions, and get and use responses.<\/div>\n

\nread<\/h2>\n
\nTo get input from the keyboard, you use the read<\/a> command. The read command takes input from the keyboard and assigns it to a variable. Here is an example:<\/div>\n
\n
#!\/bin\/bash\n\necho -n \"Enter some text > \"\nread text\necho \"You entered: $text\"\n       \n<\/pre>\n<\/div>\n
\nAs you can see, we displayed a prompt on line 3. Note that “-n” given to the echo command causes it to keep the cursor on the same line; i.e., it does not output a linefeed at the end of the prompt.<\/div>\n
\nNext, we invoke the read command with “text” as its argument. What this does is wait for the user to type something followed by a carriage return (the Enter key) and then assign whatever was typed to the variable text.<\/div>\n
\nHere is the script in action:<\/div>\n
\n[me@linuxbox me]$ read_demo.bash
Enter some text > this is some text
You entered: this is some text<\/div>\n
\nIf you don’t give the read command the name of a variable to assign its input, it will use the environment variable REPLY.<\/div>\n
\nThe read command also takes some command line options. The two most interesting ones are -t and -s. The -t option followed by a number of seconds provides an automatic timeout for the read command. This means that the read command will give up after the specified number of seconds if no response has been received from the user. This option could be used in the case of a script that must continue (perhaps resorting to a default response) even if the user does not answer the prompts. Here is the -t option in action:<\/div>\n
\n
#!\/bin\/bash\n\necho -n \"Hurry up and type something! > \"\nif read -t 3 response; then\n    echo \"Great, you made it in time!\"\nelse\n    echo \"Sorry, you are too slow!\"\nfi\n       \n<\/pre>\n<\/div>\n
\nThe -s option causes the user’s typing not to be displayed. This is useful when you are asking the user to type in a password or other confidential information.<\/div>\n
\nArithmetic<\/h2>\n
\nSince we are working on a computer, it is natural to expect that it can perform some simple arithmetic. The shell provides features for integer arithmetic<\/i>.<\/div>\n
\nWhat’s an integer? That means whole numbers like 1, 2, 458, -2859. It does not mean fractional numbers like 0.5, .333, or 3.1415. If you must deal with fractional numbers, there is a separate program called bc<\/a> which provides an arbitrary precision calculator language. It can be used in shell scripts, but is beyond the scope of this tutorial.<\/div>\n
\nLet’s say you want to use the command line as a primitive calculator. You can do it like this:<\/div>\n
\n[me@linuxbox me]$ echo $((2+2))<\/div>\n
\nAs you can see, when you surround an arithmetic expression with the double parentheses, the shell will perform arithmetic expansion.<\/div>\n
\nNotice that whitespace is ignored:<\/div>\n
\n[me@linuxbox me]$ echo $((2+2))
4
[me@linuxbox me]$ echo $(( 2+2 ))
4
[me@linuxbox me]$ echo $(( 2 + 2 ))
4<\/div>\n
\nThe shell can perform a variety of common (and not so common) arithmetic operations. Here is an example:<\/div>\n
\n
#!\/bin\/bash\n\nfirst_num=0\nsecond_num=0\n\necho -n \"Enter the first number --> \"\nread first_num\necho -n \"Enter the second number -> \"\nread second_num\n\necho \"first number + second number = $((first_num + second_num))\"\necho \"first number - second number = $((first_num - second_num))\"\necho \"first number * second number = $((first_num * second_num))\"\necho \"first number \/ second number = $((first_num \/ second_num))\"\necho \"first number % second number = $((first_num % second_num))\"\necho \"first number raised to the\"\necho \"power of the second number   = $((first_num ** second_num))\"\n       \n<\/pre>\n<\/div>\n
\nNotice how the leading “$” is not needed to reference variables inside the arithmetic expression such as “first_num + second_num”.<\/div>\n
\nTry this program out and watch how it handles division (remember, this is integer division) and how it handles large numbers. Numbers that get too large overflow<\/i> like the odometer in a car when you exceed the number of miles it was designed to count. It starts over but first it goes through all the negative numbers because of how integers are represented in memory. Division by zero (which is mathematically invalid) does cause an error.<\/div>\n
\nI’m sure that you recognize the first four operations as addition, subtraction, multiplication and division, but that the fifth one may be unfamiliar. The “%” symbol represents remainder (also known as modulo<\/i>). This operation performs division but instead of returning a quotient like division, it returns the remainder. While this might not seem very useful, it does, in fact, provide great utility when writing programs. For example, when a remainder operation returns zero, it indicates that the first number is an exact multiple of the second. This can be very handy:<\/div>\n
\n
#!\/bin\/bash\n\nnumber=0\n\necho -n \"Enter a number > \"\nread number\n\necho \"Number is $number\"\nif [ $((number % 2)) -eq 0 ]; then\n    echo \"Number is even\"\nelse\n    echo \"Number is odd\"\nfi\n       \n<\/pre>\n<\/div>\n
\nOr, in this program that formats an arbitrary number of seconds into hours and minutes:<\/div>\n
\n
#!\/bin\/bash\n\nseconds=0\n\necho -n \"Enter number of seconds > \"\nread seconds\n\nhours=$((seconds \/ 3600))\nseconds=$((seconds % 3600))\nminutes=$((seconds \/ 60))\nseconds=$((seconds % 60))\n\necho \"$hours hour(s) $minutes minute(s) $seconds second(s)\"\n       \n<\/pre>\n<\/div>\n
\n<\/div>\n
<\/span><\/div>\n","protected":false},"excerpt":{"rendered":"
The Linux Command Line by William Shotts Up to now … \u9605\u8bfb\u66f4\u591a<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[51,52,53],"class_list":["post-186","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-linux","tag-shell","tag-the-linux-command-line"],"_links":{"self":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/186","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=186"}],"version-history":[{"count":1,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/186\/revisions"}],"predecessor-version":[{"id":318,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/186\/revisions\/318"}],"wp:attachment":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=186"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=186"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=186"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}