aboutsummaryrefslogtreecommitdiffstats
path: root/shells/Makefile
diff options
context:
space:
mode:
authorsunpoet <sunpoet@FreeBSD.org>2011-10-23 15:40:59 +0800
committersunpoet <sunpoet@FreeBSD.org>2011-10-23 15:40:59 +0800
commit40a33c3b7a2a31342a7d9a1825f7ae5d485a9c68 (patch)
tree415332374f8170c6a7cf2210c16bf2600eead9c5 /shells/Makefile
parentd3d392c6515364bd5c704cfefd883a753e8d4e42 (diff)
downloadfreebsd-ports-gnome-40a33c3b7a2a31342a7d9a1825f7ae5d485a9c68.tar.gz
freebsd-ports-gnome-40a33c3b7a2a31342a7d9a1825f7ae5d485a9c68.tar.zst
freebsd-ports-gnome-40a33c3b7a2a31342a7d9a1825f7ae5d485a9c68.zip
- Add p5-Bash-Completion 0.008
bash completion should just work when you install new commands. Bash::Completion is a system to use and write bash completion rules. For end-users, you just need to add this line to your .bashrc or .bash_profile: setup-bash-complete This will load all the installed Bash::Completion plugins, make sure they should be activated and generate the proper bash code to setup bash completion for them. If you later install a new command line tool, and it has a Bash::Completion::Plugin -based plugin, all your new shells will have bash completion rules for it. You can also force immediate setup by running the same command: setup-bash-complete To write a new Bash::Completion plugin, see Bash::Completion::Plugin. WWW: http://search.cpan.org/dist/Bash-Completion/
Diffstat (limited to 'shells/Makefile')
-rw-r--r--shells/Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/shells/Makefile b/shells/Makefile
index 97acb5286337..6085ecd8efc9 100644
--- a/shells/Makefile
+++ b/shells/Makefile
@@ -25,6 +25,7 @@
SUBDIR += mksh
SUBDIR += nologinmsg
SUBDIR += osh
+ SUBDIR += p5-Bash-Completion
SUBDIR += p5-Shell-Perl
SUBDIR += p5-Term-ShellUI
SUBDIR += pdksh