Re: `&>' doesn't behave as expected in POSIX mode

2021-06-20 Thread felix
On Sun, Jun 20, 2021 at 10:18:59AM -0400, Eli Schwartz wrote: > > *Neither* behavior is similar to e.g. dash's behavior, or for that > matter ksh. Both print the uname output after registering it as a > backgrounded job (redirection does not get applied to the command itself). Quick comparission

Re: `&>' doesn't behave as expected in POSIX mode

2021-06-20 Thread Dale R. Worley
Oğuz writes: > $ set -o posix > $ uname &>/dev/null > $ > > `uname &' and `>/dev/null' should be parsed as two separate commands; > that, if I'm not missing anything, is what POSIX says. But bash > doesn't do that in POSIX mode, and redirects both stderr and stdout to > `/dev/null'. A

Re: When searching in command history, highlighting is missing the first character

2021-06-20 Thread Greg Wooledge
On Sun, Jun 20, 2021 at 07:51:03PM +0300, Teemu Leisti wrote: > Repeat-By: > 1. Open Bash, and command: abcdef > 2. Click Ctrl-R, and type: bcde > Expected behavior: The command "abcdef" is shown on the command line, > and "bcde" is highlighted. > Observed behavior: The command "abcdef" is shown on

When searching in command history, highlighting is missing the first character

2021-06-20 Thread Teemu Leisti
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall uname output: Linux work 5.11.0-18-generic #19-Ubuntu SMP Fri May 7

Re: `&>' doesn't behave as expected in POSIX mode

2021-06-20 Thread Eli Schwartz
On 6/20/21 6:30 AM, Chris Elvidge wrote: > On 20/06/2021 09:05 am, Oğuz wrote: >> $ set -o posix >> $ uname &>/dev/null >> $ >> >> `uname &' and `>/dev/null' should be parsed as two separate commands; >> that, if I'm not missing anything, is what POSIX says. But bash >> doesn't do th

Re: `&>' doesn't behave as expected in POSIX mode

2021-06-20 Thread Oğuz
20 Haziran 2021 Pazar tarihinde Chris Elvidge yazdı: > On 20/06/2021 09:05 am, Oğuz wrote: > >> $ set -o posix >> $ uname &>/dev/null >> $ >> >> `uname &' and `>/dev/null' should be parsed as two separate commands; >> that, if I'm not missing anything, is what POSIX says. But bash

Re: `&>' doesn't behave as expected in POSIX mode

2021-06-20 Thread Chris Elvidge
On 20/06/2021 09:05 am, Oğuz wrote: $ set -o posix $ uname &>/dev/null $ `uname &' and `>/dev/null' should be parsed as two separate commands; that, if I'm not missing anything, is what POSIX says. But bash doesn't do that in POSIX mode, and redirects both stderr and stdout to `/d

`&>' doesn't behave as expected in POSIX mode

2021-06-20 Thread Oğuz
$ set -o posix $ uname &>/dev/null $ `uname &' and `>/dev/null' should be parsed as two separate commands; that, if I'm not missing anything, is what POSIX says. But bash doesn't do that in POSIX mode, and redirects both stderr and stdout to `/dev/null'. Oğuz