Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -march=native -O3
uname output: Linux chatoyancy 6.5.12-100.fc37.x86_64 #1 SMP
PREEMPT_DYNAMIC Mon Nov 20 22:28:44 UTC 2023 x86_64 GNU/Linux
Machine Type: x86_64-pc-li
On 7/1/24 8:08 PM, Zachary Santer wrote:
My repeat-by does elicit both behaviors in bash 4.2. The nested
anonymous pipe (line 17) was necessary to get the diagnostic message.
All this seems to be fixed by the time we get to bash 5.2. I've
attached the repeat-by script, in case it's useful. Would
On 7/3/24 5:32 PM, alex xmb sw ratchev wrote:
is this all about adding full path ? to sourcr / . ?
for this may add one varname , like BASH_SOURCE_FULL
it seems to me , using BASH_SOURCE , if it doesnt start with / , prefix
$PWD , .. else its already
The objection is that people don't want to
On Sun, Jul 7, 2024, 21:03 Chet Ramey wrote:
> On 7/3/24 5:32 PM, alex xmb sw ratchev wrote:
> > is this all about adding full path ? to sourcr / . ?
> > for this may add one varname , like BASH_SOURCE_FULL
> >
> > it seems to me , using BASH_SOURCE , if it doesnt start with / , prefix
> > $PWD ,
On Sun, Jul 07, 2024 at 21:23:15 +0200, alex xmb sw ratchev wrote:
> hi ..
> i dont get the BASH_SOURCE[n] one
> the point of prefix $PWD/ infront of relative paths is a static part of
> fitting into the first lines of the script , assigning vars
> .. if u cd first then want the old relative path .
On Sun, Jul 7, 2024 at 2:44 PM Chet Ramey wrote:
>
> On 7/1/24 8:08 PM, Zachary Santer wrote:
> >
> > Would still like to know roughly when these issues were resolved.
>
> Why not check the releases -- with patches -- between the two? They're
> all available via git if you don't want to download t
On Mon, 8 Jul 2024, 05:23 alex xmb sw ratchev, wrote:
> i dont get the BASH_SOURCE[n] one
> the point of prefix $PWD/ infront of relative paths is a static part of
> fitting into the first lines of the script , assigning vars
>
That's not the only use case.
Consider where you have a script that
On Monday, July 8, 2024, Martin D Kealey wrote:
>
> It's not possible to change "${BASH_SOURCE[@]}" without breaking some
> existing code,
>
It's worth breaking existing code in this case.
which leaves us with some kind of explicit opt-in such as:
>
`shopt -s compat52' should suffice to opt out
