Comments on: bash programmable completion http://www.spugbrap.com/blog/2004/11/bash-programmable-completion/ This is a repository for my favorite scripts, regexes, commandlines, utilities, code snippets, tips, and other geeky things that might be useful to someone googling for an obscure solution some day. It's also a place to share my thoughts about companies I've dealt with, my favorite lifehacks, observations of interesting human behavior, clever and/or evil marketing schemes I've run across, and anything else I feel compelled to write about. Tue, 06 Jan 2009 14:30:11 +0000 http://wordpress.org/?v=2.2.3 By: ClintJCL http://www.spugbrap.com/blog/2004/11/bash-programmable-completion/#comment-8778 ClintJCL Fri, 10 Oct 2008 01:02:15 +0000 http://www.spugbrap.com/blog/2004/11/bash-programmable-completion/#comment-8778 Wow. Does that come up often enough to make a difference? I think it's really cool that the shell has an option to do this, but I have to question if the time spent coming up with a solution ever pays dividend when compared to the lost time having something come up in a tab. Type an extra letter, tab completion will go to where you want. I guess you're in situations where there are a lot instances of folders with the same name????? Is that what's happening??? Wow. Does that come up often enough to make a difference? I think it’s really cool that the shell has an option to do this, but I have to question if the time spent coming up with a solution ever pays dividend when compared to the lost time having something come up in a tab. Type an extra letter, tab completion will go to where you want. I guess you’re in situations where there are a lot instances of folders with the same name????? Is that what’s happening???

]]> By: Big Al http://www.spugbrap.com/blog/2004/11/bash-programmable-completion/#comment-8725 Big Al Tue, 07 Oct 2008 05:36:37 +0000 http://www.spugbrap.com/blog/2004/11/bash-programmable-completion/#comment-8725 Hmm, it really didn't like the code in there. Just go to the bottom of this page: http://dotfiles.org/~hanekomu/.bash_completion All is explained. No more annoying CVS directories in your tab complete. Hmm, it really didn’t like the code in there. Just go to the bottom of this page: http://dotfiles.org/~hanekomu/.bash_completion

All is explained. No more annoying CVS directories in your tab complete.

]]> By: Big Al http://www.spugbrap.com/blog/2004/11/bash-programmable-completion/#comment-8724 Big Al Tue, 07 Oct 2008 05:35:07 +0000 http://www.spugbrap.com/blog/2004/11/bash-programmable-completion/#comment-8724 Not only that, you can hack bash_completion's code to omit CVS directories, just like you wanna. Change: <code> # Use standard dir completion if no CDPATH or parameter starts with /, # ./ or ../ if [ -z "${CDPATH:-}" ] || [[ "$cur" == ?(.)?(.)/* ]]; then _filedir -d return 0 fi </code> To: <code> # Use standard dir completion if no CDPATH or parameter starts with /, # ./ or ../ if [ -z "${CDPATH:-}" ] || [[ "$cur" == ?(.)?(.)/* ]]; then _filedir -d # omit CVS directories for (( i = 0; i Courtesy of: http://dotfiles.org/~hanekomu/.bash_completion Not only that, you can hack bash_completion’s code to omit CVS directories, just like you wanna.

Change:


# Use standard dir completion if no CDPATH or parameter starts with /,
# ./ or ../
if [ -z "${CDPATH:-}" ] || [[ "$cur" == ?(.)?(.)/* ]]; then
_filedir -d
return 0
fi

To:


# Use standard dir completion if no CDPATH or parameter starts with /,
# ./ or ../
if [ -z "${CDPATH:-}" ] || [[ "$cur" == ?(.)?(.)/* ]]; then
_filedir -d

# omit CVS directories
for (( i = 0; i

Courtesy of: http://dotfiles.org/~hanekomu/.bash_completion

]]>