{"id":193,"date":"2018-10-14T01:00:00","date_gmt":"2018-10-13T17:00:00","guid":{"rendered":"https:\/\/yeslq.com\/201810193.html"},"modified":"2019-05-07T10:43:24","modified_gmt":"2019-05-07T02:43:24","slug":"the-linux-command-line-here-scripts-2","status":"publish","type":"post","link":"https:\/\/yeslq.com\/?p=193","title":{"rendered":"The Linux Command Line—Here Scripts"},"content":{"rendered":"

\nThe Linux Command Line <\/a><\/i>by William Shotts<\/span><\/h1>\n
\n
<\/span><\/div>\n
\n<\/span><\/p>\n
\nBeginning with this lesson, we will construct a useful application. This application will produce an HTML document that contains information about your system. I spent a lot of time thinking about how to teach shell programming, and the approach I have chosen is very different from most others that I have seen. Most favor a systematic treatment of shell features, and often presume experience with other programming languages. Although I do not assume that you already know how to program, I realize that many people today know how to write HTML, so our program will produce a web page. As we construct our script, we will discover step by step the tools needed to solve the problem at hand.<\/span><\/div>\n

<\/p>\n

\nWriting An HTML File With A Script<\/h2>\n
\nAs you may know, a well formed HTML file contains the following content:<\/div>\n
\n
<html>\n<head>\n    <title>\n    The title of your page\n    <\/title>\n<\/head>\n\n<body>\n    Your page content goes here.\n<\/body>\n<\/html>\n<\/pre>\n<\/div>\n
\nNow, with what we already know, we could write a script to produce the above content:<\/div>\n
\n
#!\/bin\/bash\n\n# sysinfo_page - A script to produce an html file\n\necho \"<html>\"\necho \"<head>\"\necho \"  <title>\"\necho \"  The title of your page\"\necho \"  <\/title>\"\necho \"<\/head>\"\necho \"\"\necho \"<body>\"\necho \"  Your page content goes here.\"\necho \"<\/body>\"\necho \"<\/html>\"\n       \n<\/pre>\n<\/div>\n
\nThis script can be used as follows:<\/div>\n
\n[me@linuxbox me]$ sysinfo_page > sysinfo_page.html<\/div>\n
\nIt has been said that the greatest programmers are also the laziest. They write programs to save themselves work. Likewise, when clever programmers write programs, they try to save themselves typing.<\/div>\n
\nThe first improvement to this script will be to replace the repeated use of the echo command with a single instance by using quotation more efficiently:<\/div>\n
\n
#!\/bin\/bash\n\n# sysinfo_page - A script to produce an HTML file\n\necho \"<html>\n <head>\n   <title>\n   The title of your page\n   <\/title>\n <\/head>\n \n <body>\n   Your page content goes here.\n <\/body>\n <\/html>\"\n\n<\/pre>\n<\/div>\n
\nUsing quotation, it is possible to embed carriage returns in our text and have the echo command’s argument span multiple lines.<\/div>\n
\nWhile this is certainly an improvement, it does have a limitation. Since many types of markup used in html incorporate quotation marks themselves, it makes using a quoted string a little awkward. A quoted string can be used but each embedded quotation mark will need to be escaped with a backslash character.<\/div>\n
\nIn order to avoid the additional typing, we need to look for a better way to produce our text. Fortunately, the shell provides one. It’s called a here script<\/i>.<\/div>\n
\n
#!\/bin\/bash\n\n# sysinfo_page - A script to produce an HTML file\n\ncat << _EOF_\n<html>\n<head>\n    <title>\n    The title of your page\n    <\/title>\n<\/head>\n\n<body>\n    Your page content goes here.\n<\/body>\n<\/html>\n_EOF_\n       \n<\/pre>\n<\/div>\n
\nA here script (also sometimes called a here document) is an additional form of I\/O redirection<\/a>. It provides a way to include content that will be given to the standard input of a command. In the case of the script above, the standard input of the cat command was given a stream of text from our script.<\/div>\n
\nA here script is constructed like this:<\/div>\n
\n
command << token\ncontent to be used as command's standard input\ntoken\n       \n<\/pre>\n<\/div>\n
\ntoken<\/i> can be any string of characters. I use “_EOF_” (EOF is short for “End Of File”) because it is traditional, but you can use anything, as long as it does not conflict with a bash reserved word. The token that ends the here script must exactly match the one that starts it, or else the remainder of your script will be interpreted as more standard input to the command.<\/div>\n
\nThere is one additional trick that can be used with a here script. Often you will want to indent the content portion of the here script to improve the readability of your script. You can do this if you change the script as follows:<\/div>\n
\n
#!\/bin\/bash\n\n# sysinfo_page - A script to produce an HTML file\n\ncat <<- _EOF_\n    <html>\n    <head>\n        <title>\n        The title of your page\n        <\/title>\n    <\/head>\n\n    <body>\n        Your page content goes here.\n    <\/body>\n    <\/html>\n_EOF_\n       \n<\/pre>\n<\/div>\n
\nChanging the the “<<” to “<<-” causes bash to ignore the leading tabs (but not spaces) in the here script. The output from the cat command will not contain any of the leading tab characters.<\/div>\n
\nO.k., let’s make our page. We will edit our page to get it to say something:<\/div>\n
\n
#!\/bin\/bash\n\n# sysinfo_page - A script to produce an HTML file\n\ncat <<- _EOF_\n    <html>\n    <head>\n        <title>\n        My System Information\n        <\/title>\n    <\/head>\n\n    <body>\n    <h1>My System Information<\/h1>\n    <\/body>\n    <\/html>\n_EOF_\n       \n<\/pre>\n<\/div>\n
\nIn our next lesson, we will make our script produce real information about the system.<\/div>\n
<\/span><\/div>\n","protected":false},"excerpt":{"rendered":"
The Linux Command Line by William Shotts Beginning … \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-193","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\/193","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=193"}],"version-history":[{"count":1,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/193\/revisions"}],"predecessor-version":[{"id":311,"href":"https:\/\/yeslq.com\/index.php?rest_route=\/wp\/v2\/posts\/193\/revisions\/311"}],"wp:attachment":[{"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=193"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=193"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yeslq.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=193"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}