Timeline for How to unset environment variables using a bash script
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2024 at 23:40 | comment | added | dave_thompson_085 | t: or OP at some point, possibly hours or days earlier, (1) did source/. set.sh or (2) did the assignments directly, and (much) later ran set.sh as a script and subsequently observed the envvars were (still!) set | |
| Sep 22, 2024 at 19:15 | history | edited | ilkkachu | CC BY-SA 4.0 |
added 5 characters in body
|
| Sep 22, 2024 at 17:18 | comment | added | terdon♦ | @djakkk I really, really doubt you actually successfully added the variables using that script since, as I explain in this answer, that is impossible. I am guessing you checked that the variables were set from inside the script. That would work, the variables were indeed set in the environment of the script, but only there. As soon as the script exited, the variables were gone since they only ever existed in the environment of the script. | |
| Sep 22, 2024 at 16:01 | comment | added | dja kkk | The first one, if it doesn't run, is probably because this code is abbreviated from a large section of code (the source code is generated by chatgpt and is a bit long), I'm very sorry. Then, thank you very much for your help. I successfully added the proxy using bash use_proxy.sh, which led me to believe that bash was using the current shell directly. Thanks for the correction! | |
| Sep 22, 2024 at 15:55 | history | edited | terdon♦ | CC BY-SA 4.0 |
added 50 characters in body
|
| Sep 22, 2024 at 15:48 | history | answered | terdon♦ | CC BY-SA 4.0 |