- add FAQs on $BASH_COMPLETION_DIR and rating
This commit is contained in:
parent
298fe3cce4
commit
fd1ce927d2
19
README
19
README
@ -1,4 +1,4 @@
|
||||
$Id: README,v 1.7 2002/03/02 01:09:41 ianmacd Exp $
|
||||
$Id: README,v 1.8 2002/03/11 18:53:32 ianmacd Exp $
|
||||
|
||||
|
||||
INSTALLATION
|
||||
@ -101,6 +101,23 @@ Q. How can I insert my own local completions without having to reinsert them
|
||||
A. Put them in ~/.bash_completion, which is parsed at the end of the main
|
||||
completion script.
|
||||
|
||||
Q. I author/maintain package X and would like to maintain my own completion
|
||||
code for this package. Where should I put it to be sure that interactive
|
||||
bash shells will find it and source it?
|
||||
|
||||
Put it in the directory pointed to by $BASH_COMPLETION_DIR, which is defined
|
||||
at the beginning of the main completion script. Any scripts placed in this
|
||||
directory will be sourced by interactive bash shells.
|
||||
|
||||
Q. This code is rubbish/not bad/pretty good/the best thing since sliced bread.
|
||||
How can I show my appreciation?
|
||||
|
||||
A. If you're a registered Freshmeat user take a moment to rate the project at:
|
||||
|
||||
http://freshmeat.net/rate/19041/
|
||||
|
||||
Of course, writing to me and letting me know how you feel also works.
|
||||
Patches and new completion routines are most welcome, too.
|
||||
|
||||
--
|
||||
Ian Macdonald <ian@caliban.org>
|
||||
|
Loading…
x
Reference in New Issue
Block a user