From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Best practices for managing aliases in ohmyzsh?
Date: Wed, 1 Sep 2021 12:56:34 -0700 [thread overview]
Message-ID: <079751a8-0494-0432-d4b6-f8f3e6e3e2f9@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7bS=A5yMWqcK-AZFcBe58sAtUQxjAa=rQk7RUv=zbtmeg@mail.gmail.com>
On 2021-09-01 12:16 p.m., Bart Schaefer wrote:
> No, you're still misunderstanding (or making typos). A sourced script
> DOES NOT create its own fresh environment, it affects the environment
> of the program that sources it.
>
But ... don't I recall that a script runs in a separate process? Doing
some quick looking (zsh is the same I trust):
Bash scripts are not kept in the shell’s memory. *Whenever a
script is executed, a new subshell (non-interactive shell) is
forked to execute the script.* And within the subshell, the script
is executed by the interpreter specified in the shebang line
<https://www.baeldung.com/linux/shebang> (for example,
/#!/bin/bash/). But, if required, we can also execute the script
within the current shell using the /source/ command.
(think, think, think ... )
Ok, I was too flabby in interpreting 'execute'. I've taken 'source' to
be identical to 'execute'. Not so. But ... what if you have a shebang
in a sourced file? One might suppose that forces a subshell, no?
Everything I write has the shebang, I just put it there every time.
What if you source a file with another shell's shebang? Possible
paradox there. It would *have* to run the other shell in a subshell
unavoidably there -- or just barf.
next prev parent reply other threads:[~2021-09-01 19:57 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 18:13 Steve Dondley
2021-08-30 22:27 ` Ray Andrews
2021-08-30 23:22 ` Steve Dondley
2021-08-30 23:34 ` Ray Andrews
2021-08-31 1:44 ` Steve Dondley
2021-08-31 0:14 ` Lawrence Velázquez
2021-08-31 1:29 ` Steve Dondley
2021-08-31 8:26 ` Roman Perepelitsa
2021-08-31 15:51 ` Steve Dondley
2021-08-31 17:57 ` Roman Perepelitsa
2021-08-31 18:54 ` Bart Schaefer
2021-08-31 21:22 ` Steve Dondley
2021-08-31 21:36 ` Roman Perepelitsa
2021-08-31 21:43 ` Steve Dondley
2021-08-31 21:44 ` Roman Perepelitsa
2021-09-01 0:12 ` Ray Andrews
2021-09-01 0:28 ` Bart Schaefer
2021-09-01 2:33 ` Ray Andrews
2021-09-01 3:01 ` Bart Schaefer
2021-09-01 14:20 ` Daniel Shahaf
2021-09-01 15:58 ` Ray Andrews
2021-09-01 18:22 ` Lawrence Velázquez
2021-09-01 19:11 ` Ray Andrews
2021-09-01 19:16 ` Bart Schaefer
2021-09-01 19:56 ` Ray Andrews [this message]
2021-09-01 20:03 ` Bart Schaefer
2021-09-01 20:52 ` Steve Dondley
2021-09-01 21:06 ` Ray Andrews
2021-09-01 22:06 ` Steve Dondley
2021-09-01 20:53 ` Lawrence Velázquez
2021-09-01 21:11 ` zeurkous
2021-09-01 21:19 ` Bart Schaefer
2021-09-01 21:29 ` Lawrence Velázquez
2021-09-01 21:23 ` Ray Andrews
2021-09-01 21:05 ` Ray Andrews
2021-09-01 3:19 ` Steve Dondley
2021-09-01 3:30 ` Bart Schaefer
2021-09-01 3:27 ` Lawrence Velázquez
2021-09-01 16:20 ` Ray Andrews
2021-09-01 18:34 ` Lawrence Velázquez
2021-09-01 19:19 ` Ray Andrews
2021-08-31 8:06 ` Anssi Saari
2021-08-31 15:45 ` Steve Dondley
2021-08-31 16:24 ` zzapper
2021-08-31 16:47 ` Steve Dondley
2021-08-31 17:20 ` Steve Dondley
2021-08-31 17:26 ` Bart Schaefer
2021-08-31 17:40 ` Steve Dondley
2021-08-31 17:47 ` Steve Dondley
2021-08-31 18:31 ` Ray Andrews
2021-08-31 18:59 ` Lawrence Velázquez
2021-09-01 6:40 ` Michael Klemm
2021-09-01 22:13 ` Steve Dondley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=079751a8-0494-0432-d4b6-f8f3e6e3e2f9@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).