Serious Shell Programming
  • Introduction
  • Acknowledgements
  • Basics
    • Strings
      • Single-Quotes
      • Double-Quotes
      • Unquoted Strings
      • Compound Strings
    • Here Documents
      • Here Doc
      • Indented Here Doc
      • Literal Here Doc
      • In-Memory Here Doc
    • Conditionals
      • Built-in test
      • Parameter Conditionals
      • Parameter test
    • Regex
      • grep
      • awk
      • pcre
    • Control Flow
      • Binary Operators
      • if-elif-else
      • case Statement
      • for Loop
      • while Loop
      • Functions
  • shellcheck
    • Introduction
    • Bad Advice
  • Style
    • awk
    • case
    • Redirection
    • Comments
    • trap
  • String Functions
    • substr
    • sprintf
    • replace
    • replaceall
    • replacestart
    • replaceend
    • fnmatch
  • awk
    • Pre-declaring Arrays
    • Sorting Arrays
  • Know Your limits
    • Arguments
    • Environment Variables
    • Solutions
Powered by GitBook
On this page

Was this helpful?

  1. Basics
  2. Here Documents

Literal Here Doc

When shell encounters the syntax << 'delimiter' or << "delimiter", it starts creating a multi-line buffer using these rules:

  1. A line containing exactly delimiter ends the contents

  2. Escape sequences are not expanded (e.g., \t is not translated into a literal TAB)

  3. Variables are not expanded (e.g., $foo remains $foo)

  4. Command substitutions are not performed (e.g., $(date) and `date` remain unchanged)

The buffer created is sent as stdin to the program of your choice. For example:

1 #!/bin/sh
2 cat << 'EOF'
3 $bird $(is) `\t\h\e` ${word}
4 EOF

Produces:

$bird $(is) `\t\h\e` ${word}
PreviousIndented Here DocNextIn-Memory Here Doc

Last updated 5 years ago

Was this helpful?