ack3 VS advent

fyi ack is like this but for perl instead of python https://beyondgrep.com/

If you just need a single shell command you can do :!. Example:

:!ack "stupid_structure->who_wrote_this_crap.oooohhhhh\s+="

(and if you wonder what "ack" means: https://beyondgrep.com/)

Ack is consistent with grep but will sensibly handle the recursive stuff for you.

Scan the file tree containing the website for the links, or part of tje links, for example with ack which is an easy to use, recursive reimplementation of grep.

I've thought about redoing ack in Python but it wasn't any faster than the current Perl.

Ever hear of ack it might be a faster alternative.

No, but thanks for pointing out its existence. Homepage:

https://beyondgrep.com/

(ack comes from ack-grep, a better version of grep, but you can just replace it with grep -r)

I've been a fan of ack for quite some time.  Somehow (and I'm not quite sure how) once or twice it's found stuff in source code that VSCode simply misses (likely I was searching wrong with VSCode).  And there are a few things I've found that make it even more effective in searching Elixir code that I thought I'd share.

Very much agreed. I'm a developer and I honestly prefer ack (https://beyondgrep.com/) myself. But it has the exact same issue. It's not standard.

Day 25 Solution

I can't find an answer to what causes my script to give the right answer to the example but not to the real input. The workflow looks like this: 1. the padding-character is "." 2. expand the input-matrix by 1 padding-character in each direction 3. for each pixel of the expanded image query the surrounding 8 pixels. If out of bounds add the pudding character instead. 4. flip the pudding from "." to "#" or from '#' to '.' if necessary. 5. Go back to step 2 and repeat the process with the new image

With the help of reddit users and endless patience I got this far: https://github.com/martino-vic/Advent/blob/master/day18/day18_3.ipynb It passes all the tests, *except* for the final example homework assignment, which I have saved in file "i3". I'd actually not only be curious what the bug here might be, but maybe in this case it would be more useful to learn how to debug these kind of cases efficiently. What worked until now was a print() and input() statement in the while loop so I could track step by step what is happening. But with this many additions and reductions it's simply impossible to catch a bug that way. So I'm thinking about what strategies could exist to identify a bug in a scenario like this, especially if all the previous tests (including the "slightly larger example") are passing. Any help - as always - much appreciated!

I spent the entire day with this but didn't manage to get a silver star: https://github.com/martino-vic/Advent/blob/master/day18/day18_2.ipynb I intensly hope someone can help me out... I cleaned up the code so it's easier to see what's going on. It works well until the " Here's a slightly larger example: "-part. I have the feeling it must be some trivial mistake but I can't figure it out and with my current tiredness level I've lost hope that I will. At one point the code enters an infinite loop and I can't figure out how to snap out of it. I've put an input() statement in one line, so that the while loop doesn't run away and one can track round by round what is happening. Maybe someone had some similar issue as me and can quickly point out the issue? Any hints and any help much appreciated!

Didn't manage to get a silver star, similar situation as yesterday: I get the correct output for the easier input-example and for the real input the answer is wrong and it's a complete mystery to me why. Tinkered around for 2.5h before I gave up: https://github.com/martino-vic/Advent/tree/master/day15

[2021 14 #part2] Python 3: https://github.com/martino-vic/Advent/tree/master/day14

Python 3 part1: https://github.com/martino-vic/Advent/tree/master/day14 got a silver star quite quickly by using nltk's ngrams. Part 2 tripped me up, works only for the easy input but for the proper one it gives me the wrong output, no idea why :/