- added section to KNOWN PROBLEMS about have() only checking for commands
in $PATH, so that sudo completion ccan't perform subcompletion for commands in /sbin and other such directories
This commit is contained in:
parent
8311c8438d
commit
6fecbb751c
16
README
16
README
@ -1,4 +1,4 @@
|
||||
$Id: README,v 1.4 2002/02/25 06:54:16 ianmacd Exp $
|
||||
$Id: README,v 1.5 2002/02/25 23:02:41 ianmacd Exp $
|
||||
|
||||
|
||||
INSTALLATION
|
||||
@ -87,5 +87,19 @@ I have endeavoured to trap as many instances of this in the code as possible,
|
||||
but it is highly likely that others remain. If you receive compgen errors while
|
||||
attempting completion, please report these incidents to me.
|
||||
|
||||
III.
|
||||
|
||||
The have() function is used to conserve memory by only installing completion
|
||||
functions for binaries actually present on your system. The current method of
|
||||
determining whether or not a binary is present is whether or not it is in your
|
||||
$PATH.
|
||||
|
||||
This approach has the disadvantage that sudo completion will not be able to
|
||||
perform sub-completion on, say, ifconfig if /sbin is not in your path, which,
|
||||
as an unprivileged user, it typically isn't.
|
||||
|
||||
The work-around for this is to put all directories of binaries for which you
|
||||
require completion into your $PATH variable.
|
||||
|
||||
--
|
||||
Ian Macdonald <ian@caliban.org>
|
||||
|
Loading…
x
Reference in New Issue
Block a user