On 30/06/15 02:27, Chet Ramey wrote:
> On 6/29/15 3:41 PM, Patrick Plagwitz wrote:
>
>> Bash Version: 4.3
>> Patch Level: 39
>> Release Status: release
>>
>> Description:
>> There's a bug that happens when waiting for a child process to complete
>> (via wait_for in jobs.c) that isn't part of a job
Greg Wooledge writes:
> I type:
>
> $ cat bad
>
> and press Tab twice. (The first does nothing visible.) This gives me
> two completion choices:
>
> badbad^Jfile
>
> If I press Ctrl-V Ctrl-J, the cursor moves to the next line. At this
> point, further Tabbing (with or without character
Rickard Norlander writes:
> First, run
>
> mkdir folder;cd folder;echo $'#include\nint
> main(){fopen("Hello\\nHenrik","w");}'>a.c;gcc a.c;./a.out
$ touch $'Hello\nHenrik'
> Now type
>
> cat H
>
> press tab. Result:
>
> cat He
>
> press tab twice. Two alternati
On Wed, Jul 15, 2015 at 04:28:13PM +0200, Rickard Norlander wrote:
> Description:
> If a file is created which has a newline in its filename, tab
> completion does not work correctly. The part before, and the part after the
> newline behave as separate entries for the purpose of completion.
It
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-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE
On 7/15/15 4:29 AM, Ondrej Oprala wrote:
> $ export LC_ALL=en_US.UTF-8
> $ valgrind --leak-check=full /bin/bash -c 'exit 0'
> #
> ==4190== HEAP SUMMARY:
> ==4190== in use at exit: 22,269 bytes in 614 blocks
> ==4190== total heap usage: 698 allocs, 84 frees, 29,706 bytes allocated
> ==4190==
>
$ export LC_ALL=en_US.UTF-8
$ valgrind --leak-check=full /bin/bash -c 'exit 0'
#
==4190== HEAP SUMMARY:
==4190== in use at exit: 22,269 bytes in 614 blocks
==4190== total heap usage: 698 allocs, 84 frees, 29,706 bytes allocated
==4190==
==4190== 12 bytes in 1 blocks are definitely lost in lo
