- added information to TROUBLESHOOTING section on use of set -[vx] to produce
debugging output - added information to KNOWN PROBLEMS on how the code often assumes GNU versions of various text utilitiesmaster
parent
55f9da95c5
commit
ac9ed76df4
13
README
13
README
|
@ -1,4 +1,4 @@
|
|||
$Id: README,v 1.6 2002/02/27 09:13:37 ianmacd Exp $
|
||||
$Id: README,v 1.7 2002/03/02 01:09:41 ianmacd Exp $
|
||||
|
||||
|
||||
INSTALLATION
|
||||
|
@ -57,6 +57,12 @@ Copies of the patches and prepatched versions of bash are available from:
|
|||
|
||||
http://www.caliban.org/bash/
|
||||
|
||||
If you find that a given function is producing errors under certain
|
||||
circumstances when you attempt completion, try running 'set -v' or 'set -x'
|
||||
prior to attempting the completion again. This will produce useful debugging
|
||||
output that will aid me in fixing the problem if you are unable to do so
|
||||
yourself. Turn off the trace output by running either 'set +v' or 'set +x'.
|
||||
|
||||
KNOWN PROBLEMS
|
||||
--------------
|
||||
|
||||
|
@ -81,6 +87,11 @@ 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 prior to sourcing bash_completion.
|
||||
|
||||
III.
|
||||
|
||||
Many of the completion functions assume GNU versions of the various text
|
||||
utilities that they call (e.g. grep, sed and awk). Your mileage may vary.
|
||||
|
||||
FAQ
|
||||
---
|
||||
|
||||
|
|
Loading…
Reference in New Issue