Rework "Automatic environment activation with direnv" post devenv 2.0
Nobody has claimed this yet.
- Dominant language
- Nix
- Stars
- 4k
- Forks
- 339
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 7
Description
This is more of a discussion.
Should we rework the recipe "Automatic environment activation with direnv" since devenv supports activation of a nix shell once you are inside a directory--similar to what direnv does? I'm also concerned that the integration devenv has with direnv will no longer exist in the future since it appears that it will be deprecated.
Priorities
Add 👍 to issues you find important.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the documentation recipe titled "Automatic environment activation with direnv" and read the linked devenv direnv integration page. Clarify whether the recipe remains accurate after devenv 2.0 and whether the documented integration is being deprecated; done means the recipe reflects the supported approach or is clearly marked for removal.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100