Jonas Chevalier

yes, talk to upstream so they automatically load completions in $XDG_DATA_DIRS. You can point them to this issue.

Hey Peter, It sure would be handy. If you want to contribute that feature I will gladly accept a patch. Bash can `export` functions but I don't know how it...

Hey @winmillwill , I think the idea was that in the context of a project you might want to add some shortcuts as functions or aliases that are really specific....

Some of these tickets are also placeholders for some ideas, like here I'm not super convinced it's useful but I could be convinced otherwise. Ideas are best when simmered :)

Yeah there's so many ways to do the same things but only few are good :) > I can't claim to understand the indirection you discussed about running all of...

Unfortunately BASH_FUNC_\* environment variables cause issues for other shell so we had to ignore them. See https://github.com/direnv/direnv/pull/157 If you want to maintain all your aliases in the .envrc you could...

@wbolster it seems easy on the surface but I don't know how if it will work for all shells. It also means to re-write the whole context serialisation to include...

You could `rm` the folder on each load since it's going to be recreated. ```sh alias_dir=$PWD/.direnv/aliases rm -rf "$alias_dir" export_alias() { local name=$1 shift local target="$alias_dir/$name" mkdir -p "$alias_dir" PATH_add...

``` alias_dir=$PWD/.direnv/aliases rm -rf "$alias_dir" ``` should be set in the `.envrc` so that `$PWD` resolves to the `.envrc` folder

It's unlikely that this issue will ever be solved with the current design. Environment variables are unique in the sense that they are cross-shell compatible *and* inherited in sub-shells. Direnv...