You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users can modify commands like shell-command-to-string using the inheritenv-add-advice macro.
💡 perhaps it would be nice to have a global minor mode inheritenv-mode (inheritenv-global-mode?) that does this for a reasonable default set of functions, such as shell-command-to-string, so that individuals don't have to figure out the details in the common case?
The text was updated successfully, but these errors were encountered:
Yes, that's potentially a good idea, but primarily for built-ins. Regarding other authors' packages, I think that where possible they should modify their code to do the right thing (e.g. by using inheritenv). I'd worry a little about making this package a dumping ground for workarounds. Of course, in envrc I now have a hard-coded workaround for shell-command-to-string, which is only enabled in envrc-mode, so that's kinda similar, and arguably an inheritenv-mode would be more appropriate.
If I provided such a mode, I'd do the usual thing of providing both a local minor mode and a globalized version of it, just for flexibility. envrc-mode could then unconditionally enable the local minor mode.
the readme explains that
💡 perhaps it would be nice to have a global minor mode
inheritenv-mode
(inheritenv-global-mode
?) that does this for a reasonable default set of functions, such asshell-command-to-string
, so that individuals don't have to figure out the details in the common case?The text was updated successfully, but these errors were encountered: