| lucs | Here's an example: gist.github.com/lucs/c6d470d030bc8...4dfe0f6c96 | 02:24 | |
| Going through the docs looking for something else, I found that having `--human > F` will produce the same as `--output-file=F` (the same as seen in the terminal when neither of those options is used). | 06:14 | ||
| And looking at the details of what `--human` does, I think I understand the why and how of the differences I was seeing. | 06:30 | ||
| Yay! :-) | |||
|
06:57
wayland joined
10:27
[Coke] left
10:29
[Coke] joined
13:10
ChanServ sets mode: +o lizmat
|
|||
| [Coke] | would be nice if the help gave an example of a callable for --dir | 15:22 | |
| I got an error message that --ignore-dir in rak is --dir, tried that directly, no love. | |||
| (read the help to find it's a Callable) | |||
| ah, the deny above is helpful. so rak --dir='* ne "ignored_dir"' ... | 15:24 | ||
| shouldn't rak --dir=1 "thing" search recursively? | 15:29 | ||
| (also tried --dir=True) | |||
| lizmat | trying to recollect atm | 15:34 | |
| [Coke] | I'm not blocked or anything, now down to curiosity | 15:35 | |
| lizmat | Specifying --dir as a flag will include | 15:37 | |
| *all* subdirectories, while specifying --/dir (or --not-dir) will | |||
| cause no recursion to happen whatsoever | |||
| --dir=1 is not as a flag | 15:38 | ||
| [Coke] | why is --dir=1 not a callable like --dir='*ne"skip-this"' ? | 15:39 | |
| lizmat | good question, I would have to spelunk | 15:40 | |
| please make an issue :-) | |||
| [Coke] | also --/dir=skip-dir doesn't recurse. | ||
| it only does the current dir | 15:41 | ||
| sure, opening issue. | |||
| done. | 15:42 | ||
|
17:29
lizmat sets mode: +b *!~Nemokosch@2a02:ab88:388f:5100:3f10:8b08:ff1c:706
17:55
lizmat sets mode: +b TheUnforgiven!*@*
|
|||