… about-plugin, about-alias, about-completion.
…s and completions as well.
it isn't safe to assume that symlinks created in the enabled/* dirs will be symlinks later... some users use tools like Dropbox to sync their files across systems, and these may transform symlinks into regular files. explicitly checking for symlinks with tests like [ -h $file ] will break on these systems. these tests have been replaced with [ -e $file ] instead.
The ls command in for loop has a pattern now, so full paths are returned. The user prompt and symbolic link have been updated to handle this. Also, not all plugins have '.plugin.' in the middle of their names and weren't showing up on user prompt. With this commit, everything after the first period in the file name is stripped.
since we're sourcing this as a plugin, which loads the function, it's counterproductive to also define the 'fasd' alias moving the about-plugin metadata into the case block makes this script safe for execution even if composure metadata isn't exported and available rename fasd.bash to fasd.plugin.bash to bring it inline with the other plugin scripts