On 3/3/17 9:53 PM, Misaki wrote:
> 15 Mar 2015
> bash bug
> Full-width character, followed by at least one full word with a space after
> it.
>
> Example: あa a
>
> With trailing space.
>
> Typing before the full-width character causes the 'あ' to be pushed to next
> line, with a blank space on
On 3/7/17 6:28 AM, gaze...@xmission.com wrote:
> Description:
> popd with garbage parameter removes entry from dirs but doesn't cd.
> Example: popd lsdfjlskfj
>
> Repeat-By:
> cd /some/directory
> pushd /tmp
> dirs
> popd skdfhksjdfhkjsdf
> pwd;dirs
This
On Tue, Mar 7, 2017 at 8:28 AM, wrote:
> 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'
> -DCON
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' -DPACKA
2017-03-03 08:27:03 -0500, Chet Ramey:
> On 3/1/17 4:58 PM, Stephane Chazelas wrote:
>
> > BTW, there seems to have been a regression in the handling of the -O
> > option to the bash interpreter:
>
> Thanks, I'll take a look. It looks to be specific to the various
> compat* options.
[...]
See a
