On 10 Nov 2018, G. Branden Robinson wrote:
>At 2018-11-10T15:07:23-0200, Gabriel F. T. Gomes wrote:
>> May I attribute this change to you (as commit author) in the git
>> repository for Debian's bash-completion. It would like like the
>> attached patch.
>
>I'm fine with that, but credit for id
At 2018-11-10T15:07:23-0200, Gabriel F. T. Gomes wrote:
> Hi,
>
> On 10 Nov 2018, G. Branden Robinson wrote:
>
> >Package: bash-completion
> >Version: 1:2.8-2
> >Followup-For: Bug #742466
> >
> >I'm attaching a debdiff of a proposed NMU for this.
Hi,
On 10 Nov 2018, G. Branden Robinson wrote:
>Package: bash-completion
>Version: 1:2.8-2
>Followup-For: Bug #742466
>
>I'm attaching a debdiff of a proposed NMU for this. I don't intend to
>actually NMU unless this bug threatens not to make it into the next
>D
Package: bash-completion
Version: 1:2.8-2
Followup-For: Bug #742466
I'm attaching a debdiff of a proposed NMU for this. I don't intend to
actually NMU unless this bug threatens not to make it into the next
Debian release (it's been around for several already :( ).
I hope this wi
Another way to trigger this bug is typing
for var in $(
Hi,
I encounter this bug too. The error occurs at line 560
of /usr/share/bash-completion/bash_completion.
For example, with bash launched with the -x option, the command below
produces the following output.
$ echo $(find [TAB]
Output:
+ _quote_readline_by_ref '$(find ' quoted
+ '['
Package: bash-completion
Version: 1:2.1-4
Severity: normal
Dear Maintainer,
to reproduce:
Type cat $(which b
Type [Tab].
With prior versions of bash-completions, this completed base64, basename, bash,
etc.
The current version outputs:
bash: unexpected EOF while looking for matching `)'
bash:
7 matches
Mail list logo