GitoxideLabs/gitoxide gix-command-v0.9.1

gix-command v0.9.1

on GitHub

Bug Fixes

• Derive $0 for sh -c from the shell's basename
  gix-command invokes shells as sh -c <script> <command_name> [args...],
  where the command_name operand becomes $0 inside the shell. Shells
  use $0 to prefix their own diagnostic messages (e.g.
  sh: line 1: <cmd>: command not found), so the value should identify
  the actually-running shell.

  Derive the value from the shell program itself, using the basename of
  the path passed to Command::new for the shell:

  • With the default shell on Unix (/bin/sh), $0 is sh.
  • With the default shell on Windows (sh.exe from Git for Windows),
    $0 is sh.exe, matching the launched binary's actual name.
  • With a customized shell_program, $0 reflects the chosen shell
    (e.g. bash, zsh), so its diagnostics correctly identify it.

  If the shell path has no extractable basename — Path::file_name()
  returns None for degenerate input like an empty string or / — fall
  back to _, the conventional placeholder for an unused $0 used in
  shell one-liners. This keeps the construction total without claiming a
  specific shell name.

  Using the basename also avoids an MSYS2-specific surprise on Windows:
  Cygwin/MSYS2 shells translate some command-line content received via
  lpCommandLine, including full Windows paths, so a full shell path
  passed as $0 would come back from the shell as its translated form.

  This fixes #1842. (See #1840 and #1842 regarding some of these issues.)

Commit Statistics

• 12 commits contributed to the release over the course of 28 calendar days.
• 28 days passed between releases.
• 1 commit was understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details