Kevin Tindall

thomwiggers solution worked for me too

Yes, exactly that. It was a little confusing that it did not rename `some_alias` in only the file that I'm in and files that import `some_alias`.

In my case, there was no other import of the library. Instead of ```python import os from os import pathsep as asdf ``` only ``` from os import pathsep as...

Cloud secrets may not be a possibility for some projects. Imagine laws/regulations that enforce storage of secrets to particular systems, relying on a cloud for privileged information that is outside...

Maybe there needs to be a `SECRET` command? Imagine this scenario: ``` base-aws: SECRET AWS_ACCESS_KEY_ID SECRET AWS_SECRET_ACCESS_KEY SECRET AWS_SESSION_TOKEN SECRET HAMMER_TIME=+secrets/CANT_TOUCH_THIS ``` Other targets could then base off of that.

Exactly what I was picturing, and I'll elaborate further: ``` base-a: SECRET X RUN printf "X:%s" "$X" base-b: FROM +base-a RUN printf "X:%s" "$X" # X is declared from base-a,...

- [x] relink files Definitely sounds good to me! I sometimes forget to run the link hooks (individually :frowning_face:) after a pull.

Yes, you can put all your dotfiles in one repository. See https://github.com/zeekay/dot-files as an example. From ghci to wget configuration, there is a bit of everything in there.

https://github.com/zeekay/dot-files/blob/master/ellipsis.sh has different behavior based on what operating system it is being installed on.

There is also the ability to specify a branch to checkout when installing a package. So you could possibly have different git branches representing OS specific stuff.