Anders

> I was thinking diff -u for the output Hm, ok. I thought you meant that homeshick should show what was going to be symlinked and which files would conflict....

Ah, ok. So additionally to the `[yN]` options, you'd like a `[d]` option that opens up `diff -u` and compares the file in `$HOME` with the file in the repo....

I ran into a different use-case for the same feature yesterday: At work we are going to have a local k8s setup on each machine. With the old VM setup...

OK, I rescind my +1 on this. Using patches [my specific usecase](https://github.com/kubernetes-sigs/kustomize/issues/347#issuecomment-646955396) is actually very easy to solve by templating the patch files and creating a templated kustomize overlay (using...

@MichaelJCole the patches are just as stable as the Ingress API itself, so that shouldn't be any trouble. I actually ended up creating a kustomize transformer instead (transformers and generators...

@marcelser thank you for your notes. Indeed the for loop is badly broken. The docopt works for me, but I can see that I have an additional newline before the...

`docopt.sh` itself depends on python, yes. But not the resulting script. `docopt.sh` analyzes the docstring and generates a parsing tree for that specific docstring in pure bash and then inserts...

Hey guys, thank you for the responses and thank you so much for trying it out! I agree that `docopts` and `docopt.sh` cover different use-cases: `docopts` is a more clean...

OK, I will contact @mboersma > About parsing docopt language, so you confirm you've written you own parser for docopt.sh and not using docopt python's original to achieve your goal,...

I haven't written up a post in https://github.com/kr/logfmt/issues/9 explaining why it is absolutely necessary to escape newlines. TL;DR: Unescaped newlines introduce parsing ambiguities.