On 2/2/21 1:49 PM, Lawrence Velázquez wrote:
Of course, removing this restriction opens up the possibility that a user
can shoot themselves by trying to use job control at the same time.
Remember that `job control' isn't just suspending and restarting jobs. It's
mostly about multiplexing jobs
i made an archive of both, the bugs and and this working code here
i fear the bugs will appear as soon as more complex code washes up
http://0x0.st/-ovu.bin
name: bashbugs1.tgz
or in the email as attachment
thank you
On Wed, Feb 3, 2021 at 1:05 AM Eduardo Bustamante wrote:
> On Tue, Feb 2, 20
On Tue, Feb 2, 2021 at 12:52 PM Alex fxmbsw7 Ratchev wrote:
>
> bash-5.1# n=1 bash ../ixz/paster desc 0 1 2 3
> ++ paste BEGIN ++
Could you at least use a standard archive format to send these, and
not whatever this format is? I doubt you'll get much help when the
first step is to piece together
On Tue, 2 Feb 2021, Chet Ramey wrote:
On Mon, 1 Feb 2021, Marc Aurèle La France wrote:
Currently, only the script's arguments are passed as positional
parameters. For compatibility reasons, $0 cannot be used to also pass the
script's filename, so I'm creating a new BASH_SCRIPT variable instea
bash-5.1# n=1 bash ../ixz/paster desc 0 1 2 3
++ paste BEGIN ++
++ paste BEGINFILE desc
here i reduced the stuff to minimum, aka wrote new, but the problem is here
it works
i bet till complex code
so ill go on till you read the other bug report or come up with another bug
this tree based ok ?
to
> On Feb 2, 2021, at 11:52 AM, Kevin Buchs wrote:
>
> Browsing around bashref, I found the lastpipe option and I tried it, but
> it seemed to have no effect.
>
> Rather than just submit a bug report, I thought I would try to dig in and
> find the problem and try to fix it. When I downloaded the
On 2/1/21 6:17 PM, Marc Aurèle La France wrote:
Currently, only the script's arguments are passed as positional
parameters. For compatibility reasons, $0 cannot be used to also pass the
script's filename, so I'm creating a new BASH_SCRIPT variable instead.
I'm interested in use cases for this
On 2/1/21 6:15 PM, Marc Aurèle La France wrote:
These changes are needed when building bash in a symlink shadow tree of a
read-only source tree. While there, deal with a minor typo.
Thanks for the report. This should not affect the more common build
configurations.
Chet
--
``The lyf so short
On 2/1/21 6:16 PM, Marc Aurèle La France wrote:
typemax.h states it should be included after config.h, limits.h, stdint.h,
and inttypes.h. But, on my system (with glibc 2.32), accept.c ends up
including after typemax.h, via the sequence ...
accept.c -> loadables.h -> builtins.h -> general.h ->
On 2/1/21 6:15 PM, Marc Aurèle La France wrote:
Mostly typos.
Please Reply-To-All.
Thanks for the report. At some point, --disable-multibyte is probably going
to disappear.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippo
On 2/1/21 5:29 PM, George R Goffe wrote:
Hi,
I just checked out the "latest" bash from the repo at savanna.gnu.org and am
having build problems.
I have tried --with-gnu-malloc and it's alias and also tried building without
any malloc parameters in configure without success. Enclosed below is
11 matches
Mail list logo
