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*

5
  • 2
    "For some Reason, the unmatched " inside {} is not captured by the shell parser." Is that just because syntactically, it is matched, on line 1508? i.e. the string opened on line 500 is closed on line 1508, and then another string is opened on 1508 which never gets closed. Commented Aug 8, 2019 at 12:03
  • I did not investigate the quoting behavior of bash. Bash may have multi-line quote "line1\nline2" I remember in shell you do multi-line quote with <<ENDMARK. Possibly now you can directly use double quote to quote multiple lines. This feature makes debug really hard. Commented Aug 8, 2019 at 18:22
  • 1
    I think its the best that you keep on taking backup of working copy of your script unless it gets completely ready. Commented Nov 3, 2020 at 10:43
  • Jaraws Yes, you could use source control (git) for long term tracking. For short term, don't just delete or edit lines immediately, make a copy and add comment mark at the beginning of the line. The edit the copy of the line. Some editors can recall you latest changes. Commented Nov 5, 2020 at 17:46
  • Quoting POSIX: The application shall quote the following characters if they are to represent themselves: [...] <newline> Here-doc operator (<<) is about redirection, not quoting. It treats the enclosed text as a single word though. Commented Oct 25, 2023 at 11:08