On 3/5/14 5:01 PM, Albert Shih wrote:
> If you got a file name begin with "(" the completion didn't work.
>
> For example if I do
>
> mkdir emptydir
> cd emptydir
> touch \(\)
> rm + Tab
>
> don't give me anything.
This is actually a general problem with empty completions (ty
WARNING: the codes given below cause the shell to enter an infinite
loop.
Both:
dualbus@debian:~$ bash -Tc 'f(){ :; }; trap return RETURN; f'
^C
and:
dualbus@debian:~$ bash -c 'f(){ trap return RETURN; }; f'
^C
Cause the function call to recurse infinitely. I would understand if
this is labeled
On Fri, Mar 07, 2014 at 11:38:21AM -0800, Eduardo A. Bustamante López wrote:
> WARNING: the codes given below cause the shell to enter an infinite
> loop.
>
>
> Both:
> dualbus@debian:~$ bash -Tc 'f(){ :; }; trap return RETURN; f'
> ^C
>
> and:
> dualbus@debian:~$ bash -c 'f(){ trap return RETUR
On 3/7/14 2:25 AM, Daan van Rossum wrote:
> Hi Chet,
>
> Readline 6.3 has a new bug in vi-mode:
> the "." command does no longer redo the latest "dw", "dl", "D", ... commands.
>
> Reverting back to version 6.2 fixed the issue for me.
Thanks for the report. It's the result of an overzealous atte
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash
Configuration Information
[Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-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/
On Fri, Mar 07, 2014 at 05:21:53PM +0100, Lars Wendler wrote:
> Configuration Information
> [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: x86_64-pc-linux-gnu-gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/7/14, 11:21 AM, Lars Wendler wrote:
> Bash Version: 4.3
> Patch Level: 0
> Release Status: release
>
> Description:
>
> bash-4.3 seems to expand a "~" (tilde character) with full homepath in a
> pattern substitution even when the variable is e
On 3/7/14, 2:42 PM, David Sines wrote:
> Bash Version: 4.3
> Patch Level: 0
> Release Status: release
>
> Description:
> When invoked as sh, bash 4.3.0 doesn't interpret C-style escapes
> within double-quoted substitution expansions ("${var/$'what'/ever}").
I think this is a bug; this is
