Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Respect completion-ignore-case in custom functions | Tom Ryder | 2018-10-30 | 1 | -0/+14 |
| | | | | | | This involves a little too much boilerplate for my liking, but it's still an improvement over what I had before. I might find a way to make this into a generic function. | ||||
* | Use bashdefault if available in more completions | Tom Ryder | 2017-02-12 | 1 | -1/+7 |
| | |||||
* | Ignore stderr from manpath(1) check | Tom Ryder | 2016-12-25 | 1 | -1/+1 |
| | |||||
* | Add some missing "local" calls | Tom Ryder | 2016-12-12 | 1 | -0/+1 |
| | |||||
* | Prevent man(1) completion interfering with paths | Tom Ryder | 2016-12-09 | 1 | -0/+6 |
| | |||||
* | Handle empty filename completions better | Tom Ryder | 2016-08-30 | 1 | -6/+9 |
| | | | | | | Bash 4.4 hangs in an awkward way (probably outputting the literal null char in some unexpected context) without this; I'm not sure if this is a bug or whether it's just been tolerated behaviour until now. | ||||
* | Explicitly declare array to reassure shellcheck | Tom Ryder | 2016-08-23 | 1 | -3/+2 |
| | |||||
* | Use explicit -n test within [[ ]] | Tom Ryder | 2016-08-18 | 1 | -2/+2 |
| | | | | | Bash doesn't require it, but there's no real advantage to it and it's a better habit for complying with e.g. pdksh, which does | ||||
* | Move bash completion setup into separate dir | Tom Ryder | 2016-07-30 | 1 | -0/+63 |