On 6/23/23 7:11 PM, Grisha Levit wrote:
I think we can have bash honor ignoreeof and not exit after delimiting the
token or command while not acting quite as bizarrely as ksh88.
I think the new behavior is quite reasonable. Though it does need
something to allow the exit builtin to work even
On Fri, May 26, 2023, 17:44 Chet Ramey wrote:
>
> On 4/26/23 5:38 PM, Grisha Levit wrote:
> > A few issues with EOF being received at PS2:
>
> I finally had a chance to check out the ksh88 behavior on a Solaris 10 VM.
> It's pretty bizarre, but it does point to some improvements when ignoreeof
> i
On Fri, May 26, 2023, 23:45 Chet Ramey wrote:
> On 4/26/23 5:38 PM, Grisha Levit wrote:
> > A few issues with EOF being received at PS2:
>
> I finally had a chance to check out the ksh88 behavior on a Solaris 10 VM.
> It's pretty bizarre, but it does point to some improvements when ignoreeof
> is
On 4/26/23 5:38 PM, Grisha Levit wrote:
A few issues with EOF being received at PS2:
I finally had a chance to check out the ksh88 behavior on a Solaris 10 VM.
It's pretty bizarre, but it does point to some improvements when ignoreeof
is enabled. It seems like the POSIX committee wanted the ksh
Forgot to add bug-bash.--- Begin Message ---
On 5/4/23 9:52 PM, Martin D Kealey wrote:
It's never been active in this situation, because it doesn't meet the
criteria for ignoreeof: EOF on an empty line without any command. Bash
has always done this, dating back to the late 1980s, an
On 4/26/23 5:38 PM, Grisha Levit wrote:
A few issues with EOF being received at PS2:
The setting of ignoreeof is ignored at PS2:
bash --norc -o ignoreeof
$ uname \
^D
Linux
(bash exits)
It's never been active in this situation, because it doesn't meet the
criteria for ignoreeof: EOF on an
