In the `declare -p` output, I mean:
% bash -c 'declare -A x; x=([foo]=bar [x]=y); declare -p x;'
declare -A x='([foo]="bar" [x]="y" )'
Does it serve any purpose? Just curious.
On 9/5/14, 2:57 AM, bogun.dmit...@gmail.com wrote:
> This is more or less the way I am leaning. In the next version of bash,
> it
> will be possible to set a limit on the number of recursive source/. or
> eval
> calls at compile time. This will be accomplished by changing a define
On 9/5/14, 8:26 AM, The Wanderer wrote:
> While that does address the question of what the actual length limit is,
> it doesn't address the mismatch I saw in the error message which
> occurred when the path was too long. Does that error, and the associated
> mismatch, in fact originate from within
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/05/2014 at 08:20 AM, Greg Wooledge wrote:
> On Fri, Sep 05, 2014 at 08:09:40AM -0400, The Wanderer wrote:
>
>> What exactly is the limit on the length of a shebang line in an
>> executable script, when called from within bash?
>
> Shebangs
On Fri, Sep 05, 2014 at 08:09:40AM -0400, The Wanderer wrote:
> What exactly is the limit on the length of a shebang line in an
> executable script, when called from within bash?
Shebangs are handled by the kernel, not by bash. For more details,
Sven Mascheck's page is the best out there:
http://
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
What exactly is the limit on the length of a shebang line in an
executable script, when called from within bash?
Most of what I read seems to indicate that it should be either 127
characters or kernel-dependent (and probably still 127 characters), b
