'crontab -l > foo<tab>' completes ok but 'crontab -l >| foo<tab>' does not

[jeremyhetzler]

If I have an existing file "foobar", then
crontab -l > foo<tab>
will complete "foobar" successfully.

However,
crontab -l >| foo<tab>
will not complete (finds no matches).

The >| redirection completes ok when using e.g. cat:
cat qux >| foo<tab>
completes ok.

How can I get crontab to autocomplete when using the >| redirection?

[akinomyoga]

Thank you for the report! This is because the redirection pattern in the following line is incomplete:

bash-completion/bash_completion

Line 1006 in f575693

local redir="@(?([0-9])<|?([0-9&])>?(>)|>&)"