Reproducer:
IFS=/
set a b c
cat
> On Jul 13, 2021, at 4:37 PM, Paul Gilmartin wrote:
>
> Description:
> When "word" in here-document contains command substitution,
> bash reports an error:
> here: line 4: warning: here-document at line 2 delimited by end-of-file
> (wanted `foo$( tru
bbug1
Description: Binary data
On 11/6/19 4:37 PM, Oğuz wrote:
cat <
Thanks for the report. Bash has, for some years, allowed EOF/EOS to
terminate a command substitution in certain circumstances, but this really
only shows up when you're expanding it inside a here-document. There is a
(relatively cryptic) warning message, b
cat <
On 6/29/19 1:44 PM, Denis McKeon wrote:
> Bash Version: 5.0
> Patch Level: 7
> Release Status: release
>
> Description:
>
> Bash appears to move the closing '}'
> from after a closing here-document delimiter
> to the start of the here-doc body
> (just after the opening here-docum
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions
-fstack-protector-strong -grecord-gcc-switches
-specs=/us
Garreau, Alexandre wrote:
> Subject: Editing previous lines while in here-document mode (< Not only because this is often frustrating and impractical, but also
> because this tends to cause inconsistency feeling, I think it would be
> ...
This is just my opinion but one that foll
On 5/21/18 4:40 AM, Garreau, Alexandre wrote:
> Hi,
>
> Not only because this is often frustrating and impractical, but also
> because this tends to cause inconsistency feeling, I think it would be
> useful I if you could go in the previous lines (with the left key, or
> C-p keystroke, or somethin
Hi,
Not only because this is often frustrating and impractical, but also
because this tends to cause inconsistency feeling, I think it would be
useful I if you could go in the previous lines (with the left key, or
C-p keystroke, or something alike) while writting several lines after a
here-documen
On 12/7/16 7:31 AM, andreas.l...@innovative-navigation.de wrote:
> Bash Version: 4.4
> Patch Level: 0
> Release Status: release
>
> Description:
>
> Bash removes double quotes (but not single quotes) when doing variable
> expansion with ${parameter:+word} (Use Alternate Value), in a here-documen
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/local/share
put a backslash in front of the $ so that it is not substituted when
the here document read, but later when you run that code.
On 7/9/08, Mr Aras <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've been trying to implement a "for loop" in a "here document" but the
> "name" is never assigned to any of the
On Tue, Jul 08, 2008 at 08:44:47PM -0700, Mr Aras wrote:
[...]
> #!/bin/sh
> sh <<-EOF
> for word in hello world
> do
> echo word = $word
> done
> EOF
>
> output is:
> word =
> word =
>
>
> Can someone tell me why this doesn't work? I've been going nuts trying to
> figure this one out.
[
Hi,
I've been trying to do a "for loop" in a "here document" but the variable is
never assigned to the items in the list.
e.g.
#!/bin/sh
sh <<-EOF
for word in hello world
do
echo word = $word
done
EOF
output is:
word =
word =
Can someone tell me why this doesn't work? I've been going
15 matches
Mail list logo
