completion fails on a filename that contains an equal character

2019-03-06 Thread adff
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/loca

Re: completion fails on a filename that contains an equal character

2019-03-06 Thread Chet Ramey
On 3/6/19 7:59 AM, adff wrote: > Bash Version: 4.2 > Patch Level: 46 > Release Status: release > > Description: > The bash [tab] completion as found on redhat RHEL7.6 fails with a > filename that has the = character. This happens when there are multiple > matches for the part before the = cha

Re: Bug: Bash forgets sourcefile and linenumber of read-in functions

2019-03-06 Thread Chet Ramey
On 3/5/19 12:13 AM, L A Walsh wrote: >> OK, doing that doesn't reveal any problem. If you add >> shopt -s extdebug; declare -F addnums >> to prog.sh, it prints >> >> addnums 0 environment >> > That it prints 'environment' and '0' are issues as the manpage says: > >the -F option to dec

Issue about AIX

2019-03-06 Thread REIX, Tony
Hi, On AIX, like Solaris, when root, the test "test -x /tmp/AFile" returns true even if the file is not executable. This issue is there for ages. Here attached is the patch for fixing it for v5.0 . Would you mind adding it to the source code of bash ? Thanks/Regards, Tony --- ./lib/sh/e

Re[2]: history -a misbehaves with $HISTSIZE

2019-03-06 Thread Айрат Васбикарамов
> It's in the devel branch. Try it and see if it does what you want. Yes, it does. Thanks! >Пятница, 1 марта 2019, 19:44 +03:00 от Chet Ramey : > >On 2/28/19 5:53 PM, Айрат Васбикарамов wrote: >>> It seems like what you want is min(history_lines_this_session, >>> history_offset), >>> kind of l

Re: Issue about AIX

2019-03-06 Thread Chet Ramey
On 3/6/19 10:22 AM, REIX, Tony wrote: > Hi, > > > On AIX, like Solaris, when root, the test "test -x /tmp/AFile" returns true > even if the file is not executable. > > This issue is there for ages. > > Here attached is the patch for fixing it for v5.0 . Thanks. Is this true for all versions o