Date:Mon, 29 Jan 2024 12:07:53 -0500
From:Chet Ramey
Message-ID:
| What does `wait -n' without job arguments mean?
Find, or if there are none already, wait*(2) for, a process (job technically)
that has changed state (terminated in POSIX, and one day in the NetBSD
On 1/29/24 7:54 AM, Andreas Schwab wrote:
On Jan 29 2024, Robert Elz wrote:
I always wondered why the option was 'n'
n = next?
Yes: the original implementation polled the non-terminated background jobs
and returned when one of them exited.
--
``The lyf so short, the craft so long to
On 1/29/24 12:33 PM, Chet Ramey wrote:
You should have. You told me about your implementation using `-n' in
10/2017, long before I implemented it (4/2020).
Sorry, this is my mistake. That was a different feature. Bash implemented
`wait -n' first.
For those wondering, the `different feature'
On 1/29/24 12:07 PM, Chet Ramey wrote:
On 1/29/24 7:12 AM, Robert Elz wrote:
Date: Sun, 28 Jan 2024 18:21:42 -0500
From: Chet Ramey
Message-ID: <3347f790-529b-4bee-91fd-de39bed3f...@case.edu>
| because `wait -n' doesn't look in the table
| of saved statuses
On 1/29/24 7:12 AM, Robert Elz wrote:
Date:Sun, 28 Jan 2024 18:21:42 -0500
From:Chet Ramey
Message-ID: <3347f790-529b-4bee-91fd-de39bed3f...@case.edu>
| because `wait -n' doesn't look in the table
| of saved statuses -- its job is to wait for `new' jobs to
On 1/28/24 7:19 PM, Steven Pelley wrote:
Thank you Chet for your thorough reply.
You make a few comments about differences in output (stderr for not
finding a job, notifications for jobs terminating) and in all cases I
believe you are correct. Let's assume job control is disabled.
OK, but
On Mon, 29 Jan 2024 10:30:43 -0500
Chet Ramey wrote:
> On 1/29/24 5:51 AM, Kerin Millar wrote:
>
> > $ bash -c 'declare -p BASH_VERSION; cd ""'
> > shell-init: error retrieving current directory: getcwd: cannot access
> > parent directories: No such file or directory
> > declare --
On 1/29/24 5:51 AM, Kerin Millar wrote:
$ bash -c 'declare -p BASH_VERSION; cd ""'
shell-init: error retrieving current directory: getcwd: cannot access parent
directories: No such file or directory
declare -- BASH_VERSION="5.3.0(4)-devel"
chdir: error retrieving current directory: getcwd:
On Mon, Jan 29, 2024 at 08:52:37PM +0700, Robert Elz wrote:
> Date:Mon, 29 Jan 2024 13:54:10 +0100
> From:Andreas Schwab
> Message-ID:
>
> | n = next?
This was my assumption as well.
> That would be a reasonable interpretation, I guess, but
> unfortunately not
Subject: About `M-C-e` expand result `'` failed
Configuration Information [Automatically generated, do not change]:
Machine: aarch64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -march=armv8-a -O2 -pipe -fstack-protector-strong -fno-plt
-fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat
Date:Mon, 29 Jan 2024 13:54:10 +0100
From:Andreas Schwab
Message-ID:
| n = next?
That would be a reasonable interpretation, I guess, but
unfortunately not one which helps the current question,
as it doesn't answer "next what?" It could be "the next
of these
On Jan 29 2024, Robert Elz wrote:
> I always wondered why the option was 'n'
n = next?
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
Date:Sun, 28 Jan 2024 18:21:42 -0500
From:Chet Ramey
Message-ID: <3347f790-529b-4bee-91fd-de39bed3f...@case.edu>
| because `wait -n' doesn't look in the table
| of saved statuses -- its job is to wait for `new' jobs to terminate, not
| ones that have already
Hi,
This is with commit 138f3cc3591163d18ee4b6390ecd6894d5d16977 running on Linux
6.7.2 and glibc-2.38.
$ mkdir -p ~/dir && cd ~/dir && rmdir ~/dir
$ cd ""
bash: cd: : No such file or directory
So far, so good. Now let's try to cd from a non-interactive instance.
$ bash -c 'declare -p
14 matches
Mail list logo
