Adding macro for activating parent git repo environment #396
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a macro for code I use at the top of my notebooks. It searches for a Git repository in a directory above the notebook working directory. If one is found, then it runs
Pkg.activate
on that top-level path.It partially addresses one non-default Pluto use case - storing notebooks in Git repositories. This has been discussed in [#142].
The usage is simply
@activate_repo_env
.Despite Pluto not fully understanding macros (#196), I think this macro should work. It doesn't use any outside variables, and all variables in the macro are locally scoped within a
let
block.I don't think this is an ideal fix - maybe a better solution would be to add arguments for SVN, Git, or the current working directory? Or maybe switch this from a macro to a function, or put it in a
Pluto.run
argument?