source_up_if_exists: A strict_env compatible version of source_up

[jfly]

This fixes #913

While I was in here, I opted to make the existing source_up script log
explicitly when it can't find a file. I think that's useful both with
strict_env enabled and disabled.

[zimbatm]

Thanks for the PR!

There are two minor suggestions. If you could also extend the stdlib docs in the man folder that would be perfect.

[zimbatm]

Suggested change

	local envrc file=${1:-.envrc}
	envrc=$(cd .. && (find_up "$file" || true))
	if [[ -n $envrc ]]; then
	source_env "$envrc"
	fi
	source_up "${1:-}" || true

With the above change it becomes possible to deduplicate the logic

[jfly]

That works, but with my change to source_up, it means you get a red "No ancestor .envrc found" message even though this function still succeeds.

I've tweaked things around a little bit to try to DRY this up. I'm honestly not sure if it's better or worse. What do you think, @zimbatm?

[zimbatm]

thanks, I pushed a small fixup and it's good to go

[jfly]

Thanks, @zimbatm!

[ssbarnea]

Thanks for implementing this feature, I was looking for a way to avoid a confusing warning.

[gertvdijk]

Hi @zimbatm@jfly; I just noticed you edited the generated file man/direnv-stdlib.1 instead of the source file man/direnv-stdlib.1.md for this change. Wanted to let you know for the next time.

Updated here: f58196a

And perhaps the maintainer could add a CI change to validate that the docs source->generated files are up to date (if the generated ones need to be in the repository at all...).

^{update: oops, mis-tagged the author.}

[jfly]

Oh, that's on me, not @zimbatm, sorry! I agree that this feels like an unnecessary footgun: could we get the generated files out of version control?