7 Commits

Author SHA1 Message Date
Guillaume Rousse
6a51790506 test perldoc options completion 2010-11-07 20:17:28 +01:00
Freddy Vulto
325b1c2fea (testsuite) Added expected failure for perldoc options completion
perldoc options don't complete anymore
2010-11-03 22:34:35 +01:00
Freddy Vulto
ef8b4f2722 Fix perldoc completions to run without invoking autotools
Alioth #312729

See also:
http://www.mail-archive.com/bash-completion-devel@lists.alioth.debian.org/msg02143.html
2010-10-31 23:20:19 +01:00
Freddy Vulto
51b3e20ebc (testsuite) Drop ending block comments
Instead of writing `}; # if', write just `}' as was discussed here:

    http://www.mail-archive.com/bash-completion-devel@lists.alioth.debian.org/msg01815.html
2010-06-18 17:21:38 +02:00
Ville Skyttä
c0d57b0bea (testsuite) Use File::Path instead of HTML::Parser to test perldoc.
HTML::Parser is not a "core" Perl module.
2010-01-24 23:36:01 +02:00
Freddy Vulto
6fe53ef0e6 Fixed completing perl modules containing colons
The solution for bash-4 is to remove the colon from COMP_WORDBREAKS:

   COMP_WORDBREAKS=${COMP_WORDBREAKS//:}

The workaround for bash-3, or bash-4 with a colon in COMP_WORDBREAKS,
is to call:

  __ltrim_colon_completions "$cur"

after completions have been put in COMPREPLY.

See also: E13) Why does filename completion misbehave if a colon appears
in the filename? - Bash FAQ, http://tiswww.case.edu/php/chet/bash/FAQ
2009-12-09 22:13:56 +01:00
Freddy Vulto
53b1c41c16 Reviewed tests p* 2009-07-24 11:58:02 +02:00