Re: ‘command … &’ creates subshell

From	Dmitry Alexandrov <dag@gnui.org>
Newsgroups	gnu.bash.bug
Subject	Re: ‘command … &’ creates subshell
Date	2020-07-01 18:29 +0300
Message-ID	<mailman.767.1593617396.2574.bug-bash@gnu.org> (permalink)
References	(2 earlier) <ac4a98bd-32f4-5c55-3b8f-1306e9758f54@case.edu> <7dvoi92p.dag@gnui.org> <09ea84b2-4fb1-6b05-7c0b-fe6b2ab00c6f@archlinux.org> <2643.1593599092@jinx.noi.kre.to> <pn9ffe39.dag@gnui.org>

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Robert Elz <kre@munnari.OZ.AU> wrote:
>   | > If you need to ensure a disk executable is used,
>   | Of course.  Why "command" otherwise?
>
> That doesn't actually work, "command" can run built-ins

Ah, yes, thanks for correction.

> there is actually no method ‹…› which guarantees execution of an executable from an external file, other than by using the complete path name

Well, I am not sure whether itʼs guaranteed, but the ‘exec’ as above does execute an external command in GNU Bash.

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: ‘command … &’ creates subshell Dmitry Alexandrov <dag@gnui.org> - 2020-07-01 18:29 +0300

csiph-web