[Bash-completion-devel] Bug#551780: Alternate solution -- stop resolving in bash_completion

[David Eccles (gringer)]

> This bug maybe should be moved to avahi?

The problem is in /etc/bash_completion, or at least can be fixed by modifying
/etc/bash_completion (see attached diff), so it seems reasonable to call this a
bash-completion bug. Of course, it may be that avahi-browse isn't meant to block
while waiting for resolution, which would then be an avahi bug.

My attempt at patching this removes the resolve argument (-r) from avahi-browse,
so it just spits out cached data in a parseable format (-cp).
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: avahi_nonresolve.diff
URL: <http://lists.alioth.debian.org/pipermail/bash-completion-devel/attachments/20100126/1ec92ee7/attachment.txt>