Does `wd:` in `jobs` show the current working directory of each job, or the previous working directory when invoking each job?

Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
-4
down vote
favorite
Does wd: in jobs show
- the current working directory of each job, or
- the previous working directory when invoking each job?
Can you demonstrate it or quote from some references?
I was under the impression of the second one when asking Does `ps` provide the working directory of each process?, but the replies seem all about the first one.
bash job-control
add a comment |Â
up vote
-4
down vote
favorite
Does wd: in jobs show
- the current working directory of each job, or
- the previous working directory when invoking each job?
Can you demonstrate it or quote from some references?
I was under the impression of the second one when asking Does `ps` provide the working directory of each process?, but the replies seem all about the first one.
bash job-control
I actually explicitly told Tim the answer to this, at unix.stackexchange.com/a/459033/5132 .
â JdeBP
Jul 29 at 21:11
add a comment |Â
up vote
-4
down vote
favorite
up vote
-4
down vote
favorite
Does wd: in jobs show
- the current working directory of each job, or
- the previous working directory when invoking each job?
Can you demonstrate it or quote from some references?
I was under the impression of the second one when asking Does `ps` provide the working directory of each process?, but the replies seem all about the first one.
bash job-control
Does wd: in jobs show
- the current working directory of each job, or
- the previous working directory when invoking each job?
Can you demonstrate it or quote from some references?
I was under the impression of the second one when asking Does `ps` provide the working directory of each process?, but the replies seem all about the first one.
bash job-control
edited Jul 29 at 22:28
slmâ¦
232k65479649
232k65479649
asked Jul 29 at 19:07
Tim
22.5k61222398
22.5k61222398
I actually explicitly told Tim the answer to this, at unix.stackexchange.com/a/459033/5132 .
â JdeBP
Jul 29 at 21:11
add a comment |Â
I actually explicitly told Tim the answer to this, at unix.stackexchange.com/a/459033/5132 .
â JdeBP
Jul 29 at 21:11
I actually explicitly told Tim the answer to this, at unix.stackexchange.com/a/459033/5132 .
â JdeBP
Jul 29 at 21:11
I actually explicitly told Tim the answer to this, at unix.stackexchange.com/a/459033/5132 .
â JdeBP
Jul 29 at 21:11
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Jobs prints the working directory the shell had when starting the related job.
What later happens is not in the scope of the shell.
Thanks. Can you demonstrate it or quote from some references?
â Tim
Jul 29 at 20:30
Check the last function in the file sh/xec.c from the Bourne Shell in schilytools.
â schily
Jul 29 at 20:33
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Jobs prints the working directory the shell had when starting the related job.
What later happens is not in the scope of the shell.
Thanks. Can you demonstrate it or quote from some references?
â Tim
Jul 29 at 20:30
Check the last function in the file sh/xec.c from the Bourne Shell in schilytools.
â schily
Jul 29 at 20:33
add a comment |Â
up vote
0
down vote
accepted
Jobs prints the working directory the shell had when starting the related job.
What later happens is not in the scope of the shell.
Thanks. Can you demonstrate it or quote from some references?
â Tim
Jul 29 at 20:30
Check the last function in the file sh/xec.c from the Bourne Shell in schilytools.
â schily
Jul 29 at 20:33
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Jobs prints the working directory the shell had when starting the related job.
What later happens is not in the scope of the shell.
Jobs prints the working directory the shell had when starting the related job.
What later happens is not in the scope of the shell.
answered Jul 29 at 19:22
schily
8,39221435
8,39221435
Thanks. Can you demonstrate it or quote from some references?
â Tim
Jul 29 at 20:30
Check the last function in the file sh/xec.c from the Bourne Shell in schilytools.
â schily
Jul 29 at 20:33
add a comment |Â
Thanks. Can you demonstrate it or quote from some references?
â Tim
Jul 29 at 20:30
Check the last function in the file sh/xec.c from the Bourne Shell in schilytools.
â schily
Jul 29 at 20:33
Thanks. Can you demonstrate it or quote from some references?
â Tim
Jul 29 at 20:30
Thanks. Can you demonstrate it or quote from some references?
â Tim
Jul 29 at 20:30
Check the last function in the file sh/xec.c from the Bourne Shell in schilytools.
â schily
Jul 29 at 20:33
Check the last function in the file sh/xec.c from the Bourne Shell in schilytools.
â schily
Jul 29 at 20:33
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f459217%2fdoes-wd-in-jobs-show-the-current-working-directory-of-each-job-or-the-prev%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I actually explicitly told Tim the answer to this, at unix.stackexchange.com/a/459033/5132 .
â JdeBP
Jul 29 at 21:11