The directions for the new auto-activation feature https://devenv.sh/auto-activation/ indicate users should add the devenv hook | source to their configuration file.
This certainly works, but in more declarative setups like home-manager or nixos the extra invocation of devenv to pipe to source is unnecessary.
Request
Could the hook shell scripts be exposed in the package's share like the current completion files are now, so that they can be sourced directly without needing to run devenv hook fish | source?
Some related context
Home-Manager exposes a function (lib.hm.shell.mkFishIntegrationOption which is a wrapper around mkShellIntegrationOption which is an example of this declarative style.
Of note, the direnv version of this actually just adds pkg hook fish | source, so there's precedent for the | source method, though I'd prefer to just use the file directly unless it's interpolated some way that is necessary by devenv.
The directions for the new auto-activation feature https://devenv.sh/auto-activation/ indicate users should add the
devenv hook | sourceto their configuration file.This certainly works, but in more declarative setups like home-manager or nixos the extra invocation of devenv to pipe to source is unnecessary.
Request
Could the hook shell scripts be exposed in the package's share like the current completion files are now, so that they can be sourced directly without needing to run
devenv hook fish | source?Some related context
Home-Manager exposes a function (
lib.hm.shell.mkFishIntegrationOptionwhich is a wrapper aroundmkShellIntegrationOptionwhich is an example of this declarative style.Of note, the direnv version of this actually just adds
pkg hook fish | source, so there's precedent for the| sourcemethod, though I'd prefer to just use the file directly unless it's interpolated some way that is necessary by devenv.