Hello!
How do you end the heredoc with a multiline delimiter such as the following:
cat << "a
b"
Kind regards
Nikola Novak
Sent with [Proton Mail](https://proton.me/mail/home) secure email.
Date:Fri, 14 Mar 2025 22:47:38 +0100
From:Steffen Nurpmeso
Message-ID: <20250314214738.Milbudgm@steffen%sdaoden.eu>
| I cannot reproduce this, both NetBSD sh and bash say
|
| set -- '' '' a '' '' b '' '';echo $#,$*; set -- $*; echo $#,$*
| 8, a b
| 2,a
++
On Sun, Mar 16, 2025, 12:10 AM MacBeth wrote:
> On Sat, Mar 15, 2025 at 12:33 PM Greg Wooledge wrote:
> > On Sat, Mar 15, 2025 at 16:14:00 +, Nikola Novak via Bug reports for
> the GNU Bourne Again SHell wrote:
> > > How do you end the heredoc with a multiline delimiter such as the
> fol
On Mon, Mar 10, 2025 at 10:54 AM John Wiersba via Bug reports for the
GNU Bourne Again SHell wrote:
>
> 2) However, if the alternate syntax is actively supported, then I think it
> *should* be documented, even if it is considered error-prone and if
> "best-practice" is to avoid it.
> The alterna
Date:Sat, 15 Mar 2025 23:41:45 +0100
From:Steffen Nurpmeso
Message-ID: <20250315224145.YPWRnxq7@steffen%sdaoden.eu>
| * Expands to the positional parameters, starting from one,
| initially producing one field for each positional parameter that
| is set
Date:Sat, 15 Mar 2025 23:59:24 +0100
From:Steffen Nurpmeso
Message-ID: <20250315225924.1YC4dm9D@steffen%sdaoden.eu>
| |And further, i have zero idea how shells come to the result that
| |they do if they do *not* split the fields individually. But if
| |they
Date:Sun, 16 Mar 2025 02:35:12 +0100
From:Steffen Nurpmeso
Message-ID: <20250316013512.2aC3SIyk@steffen%sdaoden.eu>
| The problem is not an empty field.
Your problem might not be, but it all derives from that.
| The problem is that ":a:" has to be splitted to ""
Robert Elz wrote in
<19942.1742090...@jacaranda.noi.kre.to>:
|Date:Sun, 16 Mar 2025 02:35:12 +0100
|From:Steffen Nurpmeso
|Message-ID: <20250316013512.2aC3SIyk@steffen%sdaoden.eu>
|
|| The problem is not an empty field.
|
|Your problem might not be, but it all
On Sat, Mar 15, 2025 at 8:18 PM Robert Elz wrote:
>
> (line joining using \ isn't technically an escape sequence, but that
> detail is irrelevant here).
>
bash(1) claims it to be:
There are three quoting mechanisms: the escape character, single
quotes, and double quotes.
A non-quote
Robert Elz wrote in
<21988.1742085...@jacaranda.noi.kre.to>:
|Date:Sat, 15 Mar 2025 23:41:45 +0100
|From:Steffen Nurpmeso
|Message-ID: <20250315224145.YPWRnxq7@steffen%sdaoden.eu>
|
|| * Expands to the positional parameters, starting from one,
|| initially
Date:Sat, 15 Mar 2025 18:08:48 -0500
From:MacBeth
Message-ID:
| However you could fake it, by including backslashes in the delimiter,
| which would allow literal newlines, but bash would ignore them as they
| are escape sequences.
bash does, so does mksh, zs
On 3/10/25 9:38 AM, John Wiersba wrote:
Maybe a comment in the documentation along the lines of:
There are also alternate, deprecated syntactic constructs for these loops
which will not be documented here
would serve both aims?
How is that better? It leads to the inevitable "well,
On Mon, Mar 10, 2025 at 5:39 PM Zachary Santer wrote:
>
> Another alternative would be for bash to print a warning whenever it
> encounters this syntax.
>
Don't do that, the one who don't care about shell portability. i.e the
script started with #!/bin/bash may well be using this construct "for
Date:Sat, 15 Mar 2025 21:54:18 -0500
From:MacBeth
Message-ID:
| bash(1) claims it to be:
Actually, I don't think it does,
| There are three quoting mechanisms: the escape character, single
| quotes, and double quotes.
|
| A non-quoted backsla
On Sat, Mar 15, 2025 at 16:14:00 +, Nikola Novak via Bug reports for the
GNU Bourne Again SHell wrote:
> Hello!
>
> How do you end the heredoc with a multiline delimiter such as the following:
>
> cat << "a
> b"
You don't.
I should have added in my last reply that if you want to investigate
field splitting, and how it works in various cases, use the expansion
of a simple variable
x=whatever
IFS=something
echo $x
or better:
args() {
printf '#=%d' "$#"
Robert Elz wrote in
<8711.1742074...@jacaranda.noi.kre.to>:
|I should have added in my last reply that if you want to investigate
Before i apologise to Greg Wooledge i want to point out that POSIX
says:
* Expands to the positional parameters, starting from one,
initially producing one fie
On Sun, Mar 16, 2025 at 04:39:33 +0700, Robert Elz wrote:
> ps: to anyone out there still reading this, when writing sh code, don't
> lapse into writing C instead, in sh, when using quotes, use '' (or \)
> whenever the quoted text is to be treated literally, and "" only when
> you are expecting exp
Steffen Nurpmeso wrote in
<20250315224145.YPWRnxq7@steffen%sdaoden.eu>:
|Robert Elz wrote in
| <8711.1742074...@jacaranda.noi.kre.to>:
...
| * Expands to the positional parameters, starting from one,
|initially producing one field for each positional parameter that
|is set. When the
Steffen Nurpmeso wrote in
<20250315225314.0SShmWUW@steffen%sdaoden.eu>:
|Steffen Nurpmeso wrote in
| <20250315224145.YPWRnxq7@steffen%sdaoden.eu>:
||Robert Elz wrote in
|| <8711.1742074...@jacaranda.noi.kre.to>:
| ...
|| * Expands to the positional parameters, starting from one,
||init
On Sat, Mar 15, 2025 at 12:33 PM Greg Wooledge wrote:
> On Sat, Mar 15, 2025 at 16:14:00 +, Nikola Novak via Bug reports for the
> GNU Bourne Again SHell wrote:
> > How do you end the heredoc with a multiline delimiter such as the following:
> >
> > cat << "a
> > b"
>
> You don't.
>
However
Date:Sat, 15 Mar 2025 19:42:54 +
From:Nikola Novak via Bug reports for the GNU Bourne Again SHell
Message-ID:
| OK, thank you!
| It's a relief, actually, to hear that. :)
The reason for this is that POSIX says (XCU 2.7.4):
The here-document shall
OK, thank you!
It's a relief, actually, to hear that. :)
Nikola Novak
Sent with Proton Mail secure email.
On Saturday, March 15th, 2025 at 6:31 PM, Greg Wooledge
wrote:
> On Sat, Mar 15, 2025 at 16:14:00 +, Nikola Novak via Bug reports for the
> GNU Bourne Again SHell wrote:
>
> >
23 matches
Mail list logo
