win10 just 0.10.6 sed output / .user.profile convention

[davehorner]

Installed just via cargo. Running the version command works fine and doesn't say anything about sed.

# just --version
just 0.10.6
# where just
C:\Users\dhorner\.cargo\bin\just.exe

using the keybase example renamed to justfile. The default recipe works fine. With no arguments in a directory with no justfile, I get information about a sed invalid option E and something about "cargo ltest". I have no idea why I would be getting any output from sed?!

# just
sed: invalid option -- E
Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...

  -n, --quiet, --silent
                 suppress automatic printing of pattern space
  -e script, --expression=script
                 add the script to the commands to be executed
  -f script-file, --file=script-file
                 add the contents of script-file to the commands to be executed
  -c  --nocr     turn off \r$ translation; must be first switch on command line
      --help     display this help and exit
  -V, --version  output version information and exit

If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret.  All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.

E-mail bug reports to: [email protected] .
Be sure to include the word ``sed'' somewhere in the ``Subject:'' field.
cargo ltest
error: no such subcommand: `ltest`

        Did you mean `test`?
error: Recipe `test` failed on line 18 with exit code 101

[casey]

Are you calling just from a checkout of the just project itself? If so, then you have the project justfile in a parent directory, which calls sed -E.

[davehorner]

Thank you, that was what I was running into! :)

I am trying to get system wide recipes via a .user.justfile in my %USERPROFILE% directory. just is not seeing the recipes in the .user.justfile.

[casey]

Thank you, that was what I was running into! :)

Nice, glad you got it working.

I am trying to get system wide recipes via a .user.justfile in my %USERPROFILE% directory. just is not seeing the recipes in the .user.justfile.

You'll need to invoke just via an alias to pick up those recipes:

alias .j='just --justfile ~/.user.justfile --working-directory .'

[davehorner]

Is there an issue with having just pull in the .user justfile automatically?

alias / doskey / Set-Alias etc work in the shell but not ideal (invoking from script using system just); would expect user profile files to apply to the user.

--justfile ~/.user.justfile is a strange convention if it requires it to be fully specified.

[casey]

I think this comes closest: #1036

It would allow putting fallback recipes in ~/.justfile.

[davehorner]

I'm uncertain at this time how to go about doing that. I will watch the issue; it's really not a huge deal, I was just interested to see how the profile would work. thanks for the responses.