On 4/19/21 11:09 AM, konsolebox wrote:
Attached patch demonstrates a solution that solves the current issues
of unset discussed in
https://lists.gnu.org/archive/html/bug-bash/2021-03/msg00056.html
while avoiding breakage of scripts and keeping the expansion of
subscripts consistent with expansion
On 4/25/21 11:53 AM, Eli Schwartz wrote:
Interestingly, it doesn't seem to be including the default loadablesdir
defined in Makefile.inc and bash.pc, but hardcodes several paths used in
common configurations to be overridden in a similar manner to
-DDEFAULT_PATH_VALUE=...
The first path elemen
On 4/25/21 11:44 AM, Eli Schwartz wrote:
>> This commit to the development branch adds a default value for
>> `BASH_LOADABLES_PATH':
>>
>> https://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=fb4ddc2d2b66b776e013ddadfce86270a71c323a
>>
>> So in the next version you will be able to use them
On 4/25/21 11:41 AM, Oğuz wrote:
> 25 Nisan 2021 Pazar tarihinde Eli Schwartz yazdı:
>
>> The bash loadables available in the standard make install seem pretty
>> useful and people might actually want to use them in scripts. But
>> scripts cannot easily know *where* they are located.
>>
>>
>> In
25 Nisan 2021 Pazar tarihinde Eli Schwartz yazdı:
> The bash loadables available in the standard make install seem pretty
> useful and people might actually want to use them in scripts. But
> scripts cannot easily know *where* they are located.
>
>
> In the bash manpage is documented:
>
> BASH_LO
The bash loadables available in the standard make install seem pretty
useful and people might actually want to use them in scripts. But
scripts cannot easily know *where* they are located.
In the bash manpage is documented:
BASH_LOADABLES_PATH
A colon-separated list of directories in which t
thank you
he added, akso unicodes it seems not to complete
peace
On Sat, Apr 24, 2021, 23:14 Chet Ramey wrote:
> On 4/23/21 5:02 PM, Alex fxmbsw7 Ratchev wrote:
> > mkdir ttt ; cd ttt
> > printf 'printf success' >some\'thing
> > chmod +x *
> > ./tabtab == nothing
>
> Thanks for the report.
>
