Ive tried using path and exact variants to no avail.

# /home/pbaum/.config/direnv/direnv.toml

[whitelist]
prefix = [ "/mnt/data/filesystem/home/x/Development/hosts" ]
prefix = [ "/home/x/Development/hosts" ]
exact = [ "/mnt/data/filesystem/home/x/Development/hosts/hc1/.envrc" ]
exact = [ "/home/x/Development/hosts/hc1/.envrc" ]

$ cd /home/x/Development/hosts/hc1
$ direnv

I am wondering if autoenv could not be used in complex CI environments where we have multiple steps and where we need to save/restore status between different steps.

We are currently doing appending variables inside some env_jenkins.properties files and on some some steps (builders) and on others we do source env_jenkins.properties in order to load them.

If autoenv would work also for

In case you find it useful, we're using this extension. Just not to forget $set!

DBCollection.prototype.set = function(query, setUpdates) {
    return this.update(query, {$set:setUpdates}, false, true);
};

Filtering by command is great, but how about also filtering by currently active directory?
I've quickly hammered something into place that works using preexec...

# Added to end of  ~/.bashrc

__peri_filter_preexec() { if [[ "${PWD}" =~ .*Private.* ]] ; then __BH_SAVE_COMMAND=''; fi }
if [ -f ~/.bashhub/deps/bash-preexec.sh ]; then source  ~/.bashhub/deps/bash-preexec.sh ; preexec_f

I'm packaging modernish for FreeBSD now. Usually, we put examples under share/examples/name, documentation under share/doc/name and any other data, that do not belong to any of the aforementioned directories, into share/name.

I wonder if you'd like to follow the same convention in this repository.

The reason is that I am not sure if I should move modernish examples to a standard pla