Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • @Tigger: That's not how here-docs work. Quoting the limit string (first EOF) means that parameter substitution is suppressed for the content of the here-doc. The quotes are not part of the limit string. See tldp.org/LDP/abs/html/here-docs.html. Commented Dec 13, 2017 at 1:17
  • Another thing clouding this issue is that you're using peculiar formatting. Please use code blocks, not block quotes. Just take the original text copy-pasted from your terminal, and insert four spaces at the beginning of every line. (You can do it in a gVim buffer with :%s/^/ / where there are four spaces between the final two slashes.) Commented Dec 13, 2017 at 5:02
  • @Wildcard: I would normally do as you suggest. I recognize it was peculiar formatting, but it was a (possibly misguided) attempt to make it clear what was actually being typed in light of the fact that novice *nix users will not necessarily recognize the '> ' as a secondary prompt. Code blocks don't provide such flexibility, AFAIK. Commented Dec 13, 2017 at 5:12
  • 1
    I've converted my "code" samples to block code formatting as per Wildcard/muru requests. As expected, the broken SE syntax colouring now indicates to inexperienced eyes that the '> ' prompts are part of typed strings and the warning messages further destroy any highlighting utility. Commented Dec 13, 2017 at 5:45
  • 1
    I turned off the syntax highlighting. Your points about its faults are quite valid, though. I've done some research and opened a thread on Meta about it. Commented Dec 13, 2017 at 7:11