sorry for the typo in the title, it should be *lowest*.
On Wed, Oct 2, 2019 at 8:35 AM hk wrote:
> Configuration Information :
> Bash Version: 5.0
> Patch Level: 0
> Release Status: release
>
> Description:
> the code snippet from expr.c starting from line 141:
>
>> /* This should be the functio
Configuration Information :
Bash Version: 5.0
Patch Level: 0
Release Status: release
Description:
the code snippet from expr.c starting from line 141:
> /* This should be the function corresponding to the operator with the
>highest precedence. */
> #define EXP_HIGHEST expcomma
Am I understa
*Configuration Information [Automatically generated, do not
change]:Machine: x86_64OS: linux-gnuCompiler: gccCompilation CFLAGS: -g -O2
-fdebug-prefix-map=/build/bash-LQgi2O/bash-5.0=. -f$uname output: Linux
amdubuntu 5.0.0-29-generic #31-Ubuntu SMP Thu Sep 12 13:05$Machine Type:
x86_64-pc-linux-gn
On 9/30/19 5:52 PM, Len Trigg wrote:
> Hi,
>
> I submitted a patch to savannah a few months ago that exposes READLINE_MARK
> in addition to the existing READLINE_POSITION. There has been no feedback
> on it so I'm wondering if that's not the normal workflow for submitting
> patches. Should they in
On 10/1/19 7:14 AM, L A Walsh wrote:
> On 2019/09/30 14:39, Grisha Levit wrote:
>> A few of the recently-added shopt options aren't getting reset when
>> running a shebang-less script, this should fix it up:
>>
> Suppose the shebang-less script is being run by an earlier version
> of bash. Won'
On 9/30/19 5:39 PM, Grisha Levit wrote:
> A few of the recently-added shopt options aren't getting reset when
> running a shebang-less script, this should fix it up:
Thanks for the report.
> Maybe verifying this is something that can be added to the test suite?
> Something like:
Yes, something l
On 9/30/19 8:39 PM, Geoff Kuenning wrote:
> $'\361' is a valid character in Latin-1, which is how it happened to arise
> in my case. Also, I tested with the C locale, which should be agnostic to
> character encodings, and got the same result.
That's the strange part. I can't reproduce this with t
On Tue, Oct 01, 2019 at 04:14:00AM -0700, L A Walsh wrote:
> On 2019/09/30 14:39, Grisha Levit wrote:
> > A few of the recently-added shopt options aren't getting reset when
> > running a shebang-less script, this should fix it up:
> >
> Suppose the shebang-less script is being run by an earlier
On 2019/09/30 14:39, Grisha Levit wrote:
> A few of the recently-added shopt options aren't getting reset when
> running a shebang-less script, this should fix it up:
>
Suppose the shebang-less script is being run by an earlier version
of bash. Won't the new patch radically change the behavior
