Age | Commit message (Collapse) | Author | Lines |
|
|
|
|
|
|
|
Only remaining problem:
If the current relative path is shorter than a file's relative path, some ../'s might be missed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This adds the handling of ../, currently with at least these problems:
- ../ only completes to ../.. if ../.git does not exist (until ..../.git does exist)
- if etc/foo/bar was modified, and pwd is etc, git add will *only* complete to ../etc/foo/bar
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A quite ugly solution, but the best I could think of
(and still better than [[ -r $file ]] && source $file or source $file &> /dev/null, IMHO)
|