Bug#352048: bash: sudo completion always fails the first time

2006-02-12 Thread Ruben Porras
Am Donnerstag, den 09.02.2006, 12:25 -0500 schrieb Justin Pryzby: for example 000: 7375 646f 2053 7461 7274 2e70 6d20 0asudo Start.pm . That one has 2 spaces in it (0x20), as expected, and a newline (0x0a). Did that instance of the command actually fail, after C-xC-e returned? Yes,

Bug#352048: bash: sudo completion always fails the first time

2006-02-09 Thread Ruben Porras
Package: bash Version: 3.1-2 Severity: normal Sudo completion always fails the first time, for example: $ sudo ./qemu.sh Password: sudo: unable to execute ./qemu.sh: No such file or directory (Up arrow pressed) $ sudo ./qemu.sh bridge name bridge id STP enabled interfaces

Bug#352048: bash: sudo completion always fails the first time

2006-02-09 Thread Justin Pryzby
On Thu, Feb 09, 2006 at 11:42:08AM +0100, Ruben Porras wrote: Package: bash Version: 3.1-2 Severity: normal Sudo completion always fails the first time, for example: When are you using completion? As in sudtab or sudo ./qumutab? Could you edit the command with vim (C-xC-e) and !!xxd to get

Bug#352048: bash: sudo completion always fails the first time

2006-02-09 Thread Ruben Porras
Am Donnerstag, den 09.02.2006, 09:41 -0500 schrieb Justin Pryzby: On Thu, Feb 09, 2006 at 11:42:08AM +0100, Ruben Porras wrote: Package: bash Version: 3.1-2 Severity: normal Sudo completion always fails the first time, for example: When are you using completion? As in sudtab or sudo

Bug#352048: bash: sudo completion always fails the first time

2006-02-09 Thread Justin Pryzby
On Thu, Feb 09, 2006 at 05:39:07PM +0100, Ruben Porras wrote: Am Donnerstag, den 09.02.2006, 09:41 -0500 schrieb Justin Pryzby: On Thu, Feb 09, 2006 at 11:42:08AM +0100, Ruben Porras wrote: Package: bash Version: 3.1-2 Severity: normal Sudo completion always fails the first