| 17 Feb 2025 | |||
| [Coke] | doesn't look like that's actually a dep? | 19:10 | |
| ok. | |||
| lizmat | or somewhere hmmm... | 19:11 | |
| raku.land/zef:lizmat/path-utils#path-is-text | 19:12 | ||
| [Coke] | path-is-text returns 0 on that file | ||
| lizmat | ah.... weird | 19:13 | |
| [Coke] | my command line was 'rak --under-version-control rc' - does that option override text? | ||
| lizmat | ah, yes... try adding --is-text ? | 19:14 | |
| [Coke] | much better. | 19:15 | |
| Probably LTA that trying to search the binary file explodes rak instead of ignoring/warning on the file. | |||
| lizmat | yeah, I think there is an issue for that already | ||
| if not, there should be one :-) | |||
| [Coke] | heard. ;) | 19:17 | |
| 16 May 2025 | |||
| wayland | Hi! I'm looking for something that prints all the lines from STDIN until there's a match, and then it prints another say 5 lines, and then exits. | 07:47 | |
| (I'm wanting to find the first "Not OK" test, and a few lines after) | 07:48 | ||
| I've read about the --also-first option, and it doesn't quite seem to do what I want | 07:49 | ||
| lizmat | hmmm that's not possible with rak at the moment, it would require a new context handler | 08:47 | |
| wayland | Currently using: | perl -pe '/not ok/ and $f=1; $f and do { $f++; $f > 6 and exit; }' | 09:22 | |
| Anyway, thanks for saving me the trouble of looking further :) | |||
| lizmat | I guess one could possible want the opposite as well: don't print the lines until there is a match, but then print them all (and possibly N lines before the match) | 10:25 | |
| wayland76 | Yes, agreed; but the X lines before/after is already possible, so it's only the "do/don't print until first/last match" part is needed. | 11:03 | |
| 11 Jul 2025 | |||
| samebchase | Hi, I've noticed that when I pipe the output of rak to some other tool (head, choose etc.), I get an error, but without piping the output there's no error. Will file a proper bug report once I'm at a usable computer. | 05:51 | |
| It's been helping me at work. Thanks for making it lizmat! 💯 | |||
| [Coke] | What's the error? | 13:23 | |
| I occasionally get Too many open files | |||
| because my shell has bad defaults | |||
| 12 Jul 2025 | |||
| samebchase | Yeah, it's usually that for me | 17:26 | |
| Then I do the ulimit thing | |||
| Sometimes a "broken handle" or something when I pipe the output | 17:27 | ||
| Will get the exact logs | |||
| [Coke] | cool | 23:08 | |
| 21 Aug 2025 | |||
| # Actually rak - provided by App::Rak 0.3.19, running Raku 6.d with Rakudo 2025.05. | 16:48 | ||
| /Users/coke/sandbox/scripts/ack: line 8: 25712 Segmentation fault: 11 rak "$@" | |||
| Welcome to Rakudo™ v2025.05. | |||
| lizmat | interesting, and I guess repeatable ? | 16:56 | |
| [Coke] | ... huh. no, I was unable to repro it | 18:14 | |
| weird. | |||
| lizmat | 2025.06 had a return frame fix in by patrickb: I wouldn't be surprised if that killed a gremlin | 18:19 | |
| [Coke] | cool cool | 18:27 | |
| 5 Oct 2025 | |||
| Hi. Is there a way to get '§' as a command line option instead of part of the search terms | 16:57 | ||
| lizmat | what are you trying to do, and doesn't do what you want/expect? | 17:06 | |
| 9 Oct 2025 | |||
| [Coke] | I want to do something like ack's -w. | 15:24 | |
| and because it's not a parameter but part of the search criteria, I cant save it as an alias. | 15:25 | ||
| maybe it's already in there somewhere, there are a lot of options! | |||
| so 'rak -w word' is my end goal. | 15:33 | ||
| but right now I only see how to do that as rak §word | |||
| (which I can type on this keyboard but is much slower. :) | 15:34 | ||
| lizmat | rak --type=word word | 17:43 | |
| rak --type=words word | |||
| [Coke] | See, I'm just lazy and not reading the docs. | 18:47 | |
| lizmat++ | |||
| now I can use my muscle memory for ack -wi, whee | 18:49 | ||
| lizmat | :-) | 18:52 | |