Setting/unsetting posix mode interferes with keybindings

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'

compgen -d odd symlink behavior

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'

[PATCH] Spelling fixes

--- CHANGES | 22 +++--- CWRU/changelog | 8 NEWS| 6 +++--- bashhist.c | 2 +- bashline.c | 4 ++-- builtins/gen-helpfiles.c

Completiong for first word invoked even when cursor is before the first word

Hello, Completion functions seem to be invoked for the first word even when the cursor is before that word. For example: $ foo() { echo ; echo completing; } $ foo # hit Ctrl-A to go to beginning of line (before foo), then Tab completing Same thing if there's whitespace before the first word

Re: Case (in)sensitivity of complete -X patterns?

On Saturday 18 September 2010, Chet Ramey wrote: On 9/16/10 2:19 PM, Ville Skyttä wrote: Hello, I was looking for a way to make complete/compgen -X filter patterns case insensitive, but it seems that the -X patterns are not affected by nocaseglob nor nocasematch, is that correct

Negative COMP_CWORD values?

Hello, Is it intentional that COMP_CWORD may have a negative value within a completion function? I did not find any indication of that in the bash man page. For example: foo() { echo COMP_CWORD:$COMP_CWORD } complete -F foo bar Then, type bar (sans quotes, two

Re: Non-filename completions containing slashes and -o filenames

On Monday 15 June 2009, Chet Ramey wrote: Ville Skyttä wrote: Hello, Apologies if this is not an appropriate list to post a question like this (pointers elsewhere welcome), but here goes: I'm trying to figure out how to do the right thing with non-filename completions containing

Non-filename completions containing slashes and -o filenames

Hello, Apologies if this is not an appropriate list to post a question like this (pointers elsewhere welcome), but here goes: I'm trying to figure out how to do the right thing with non-filename completions containing slashes in a function that was passed to complete along with -o filenames.