Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #11522
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Misused term "subshell" in §3.3 of the Bash Manual |
| Date | 2015-09-21 08:49 -0400 |
| Message-ID | <mailman.1529.1442839788.19560.bug-bash@gnu.org> (permalink) |
| References | <726AC67C-1BA2-46B5-B9A3-B9263EDCD82C@qq.com> |
On Mon, Sep 21, 2015 at 07:45:25PM +0800, ziyunfei wrote: > "Functions may be exported so that *subshells* automatically have them defined with the -f option to the export builtin" > > Technically, a child shell process forked/execed by the current shell is not a real subshell, am I right? I agree with you, but it's not clear what the best wording should be. Exported functions only work when the (grand)child process receiving them is another instance of bash. Maybe: Functions may be exported, using the -f option to the export builtin, so that they are automatically defined in all child bash shells.
Back to gnu.bash.bug | Previous | Next | Find similar
Re: Misused term "subshell" in §3.3 of the Bash Manual Greg Wooledge <wooledg@eeg.ccf.org> - 2015-09-21 08:49 -0400
csiph-web