-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
justfile_directory() -> canonical_justfile_directory() #2018
Comments
Can you provide steps to reproduce the issue? I was able to create a justfile, symlink it to Is the goal to have I think you could use:
Does that work for you? |
this line fails:
|
this works to get the canonical justfile-directory:
with a symlinked justfile in the root of the linux filesystem
but now I want to use this variable to import justfiles from
|
or
gives:
|
Note that imports are currently happening relative to the non-canonical justfile-dir. (I started out using multiple symlinks, ending up with a symlink in /) directory-structure (in a docker)
in /etc/justfile imports relative to the canonical location of the justfile fail
|
Gotcha, that makes sense. Whoops, yeah, I meant Hmm, this is a tricky one. Could you make your justfile like this:
Instead of a symlink? |
usecase: I started to make a symlink to my justfile in the root of my filesystem /
to have access to my just-recipes from anywhere.
in this case the justfile is a symlink, this introduces an error justfile_directory() which is not resolved
It would be nice the have a resolved canonical directory "canonical_justfile_directory()"
The text was updated successfully, but these errors were encountered: