Timeline for Why does bash clear OLDPWD when a child script is started?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 12:04 | history | edited | CommunityBot |
Commonmark migration
|
|
| Nov 26, 2015 at 19:15 | vote | accept | jrw32982 | ||
| S Nov 15, 2015 at 1:38 | history | suggested | user79743 | CC BY-SA 3.0 |
Correct link, better colors by lang=c.
|
| Nov 15, 2015 at 1:36 | review | Suggested edits | |||
| S Nov 15, 2015 at 1:38 | |||||
| Nov 14, 2015 at 19:36 | comment | added | Thomas Dickey |
The way to resolve whether it was intentional or merely a minor bug overlooked for 25 years would be to file a bug report. Since the initial value of OLDPWD does not appear to be addressed by POSIX, the guiding constraint would be whether bash's developers intended to match the behavior of ksh, or not.
|
|
| Nov 14, 2015 at 19:20 | comment | added | jrw32982 |
Based on bash's behavior, it appears that although OLDPWD is exported by bash properly, bash refuses to import it into a new process (bash appears to unset OLDPWD upon entry).
|
|
| Nov 14, 2015 at 19:13 | comment | added | jrw32982 |
"no prior cd command"...I remember a shell on Solaris where PWD was not set upon shell entry. I believe it was later fixed.
|
|
| Nov 14, 2015 at 2:27 | history | edited | Thomas Dickey | CC BY-SA 3.0 |
clarify
|
| Nov 14, 2015 at 2:18 | history | answered | Thomas Dickey | CC BY-SA 3.0 |