git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-gui (Windows) bug report

From
Mmbrenner@sftnj.com <mbrenner@sftnj.com>
Date
Apr 26, 2023, 17:14 UTC
Message-ID
<005601d97862$869fad80$93df0880$@sftnj.com>
Git-gui (windows) action "Explore working copy" fails.

What did you do before the bug happened? (Steps to reproduce your issue) Opened a repository using git-gui (On Windows server 2019) Selected "Repository" then "Explore working copy"

What did you expect to happen? (Expected behavior) File Explorer (explorer.exe) should open in the working directory

What happened instead? (Actual behavior) Error dialog appears with message "Error: explorer.exe not found in PATH"

What's different between what you expected and what actually happened? Explorer.exe is in the PATH in Windows and running the command displayed in the detail of the error in GIT-BASH "exec explorer.exe {C:\Shares\SFT04\G\gitrepo\SCloud2\SCVPortal} &" yields the desired result. (explorer.exe launches, displaying the working directory)

Anything else you want to add:

Please review the rest of the bug report below. You can delete any lines you don't wish to share.

[System Info] git version: git version 2.40.1.windows.1 cpu: x86_64 built from commit: ceee26d5cac05a3437097b43d034c4ad2e99d571 sizeof-long: 4 sizeof-size_t: 8 shell-path: /bin/sh feature: fsmonitor--daemon uname: Windows 10.0 17763 compiler info: gnuc: 12.2 libc info: no libc information available $SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe

[Enabled Hooks]
Message 1 of 1 in “git-gui (Windows) bug report”
  1. mbrenner@sftnj.comApr 26, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.