Ivan Zahariev a écrit :
> Same here, as Marc said.
>
> I think that usually we are reading the script from a file and this is
> the use-case we must focus on. Currently, we have the problem I
> described when executing a script from a file and I think this must be
> fixed/changed.
Hey, wait.
On Aug 5, 2:05 pm, Marc Herbert wrote:
> I am not sure I get this... first of all, the script itself is usually
> not read from stdin (but from fd 255 in bash).
>
> Now considering the seldom cases where the script is actually read from
> stdin, are you saying that: it is a wanted feature that s
> make it disabled by default...
>>
>> The problem is that Bash does not read up the whole script which it is
>> currently executing.
>> As a result of this, if we update the script file with a newer version
>> while it is running, this may lead to unpredicted resul
On Tue, Aug 04, 2009 at 08:23:16AM -0700, John Reiser wrote:
> On 08/04/2009 12:48 AM, fam...@icdsoft.com wrote:
> > The problem is that Bash does not read up the whole script which it
> > is currently executing.
> > As a result of this, if we update the scr
Bash does not read up the whole script which it is
currently executing.
As a result of this, if we update the script file with a newer version
while it is running, this may lead to unpredicted results.
It is an intended design feature that the shell reads only as much as necessary
to proce
c-linux-gnu
Bash Version: 3.2
Patch Level: 48
Release Status: release
Description:
First I would like to say that I'm not sure if this is a bug or a
feature of Bash.
If it is a feature, please let me know how to turn it off; or better
make it disabled by default...
