On Windows Terminal / Powershell session running crush, unable to launch crush within separate directory

[outwebbed]

Describe the bug

On Windows 11 I have the crush.exe extracted to a directory within my Program Files/ path. In order to run crush in any directory, I create a powershell alias. When I did so, crush would successfully attempt to start...but then fail noting that it could not find the sqlite3 database.

In order to run crush from any directory I have setup a Powershell profile alias function, and I have crush successfully running in any directory. But the directory/path that is provided to the context is the original executable location/path e.g. within /Program Files/.

Then, in order to get crush to include the actual directory I was working in into its context, say a codebase/local git repository, I have to manually tell crush to include via the absolute path.

While not a huge pain...it would feel like a nicer experience if I could simply run crush in any directory and that cwd automatically is added to the crush session context.

Looked into possibly providing some parameter to the crush command by way of the powershell alias function but I don't believe crush has any parameter support?

Setup

Please complete the following information along with version numbers, if applicable.

• OS Windows 11
• Shell: Powershell
• Terminal Emulator: Wave + Windows Terminal
• Crush version: 0.6.2

Note: you might encounter rendering issues if your locale does not use
UTF-8 encoding. Please check your locale (locale on POSIX systems) to
see what encoding is being used by your system.

To Reproduce

Steps to reproduce the behavior:

1. Go to Run crush via a powershell alias (that maps crush to the crush.exe executable in the original dir) in any directory and ask crush about your cwd (which again will be crush since the powershell function will cd to the crush executable path so it will run successfully, otherwise crush will not be able to find the sqlite3 database file.)

In relation to the issues I'm having, I asked crush to explain why there are some problems with how it operates on Windows:

│ can you explain the issue you are having with bash commands in this current session

I'm encountering two primary issues with bash commands in this session:

1. cd Command Failure: The cd command does not reliably change the current working directory,
   even when provided with an absolute path. My internal "current working directory" (as reported by
   pwd ) remains unchanged, causing tools that rely on a relative path from this assumed cwd to
   fail.
2. crush.exe Execution Failure: I'm unable to directly execute crush.exe with arguments (e.g.,
   --help , --version ) using its absolute path within the bash tool. The system reports
   "executable file not found" or "not found," which is unexpected given that ls can correctly list
   the contents of the directory where crush.exe resides.

These issues indicate a limitation or unexpected behavior in how the bash tool's internal shell
environment interacts with the Windows filesystem and manages its working directory and executable
paths. As a result, I must rely solely on explicit absolute paths for all file system interactions.

And in general, I asked crush the above query after I made a simply instruction to tell me which version of crush it was using, and the response was:

 ✓ Bash C:/Program Files/charm/crush/crush.exe --version

    not found
   
    Exit code 127                                                                                  

I'm having trouble retrieving my version information directly through the bash tool, even with
the full path to the executable. The command appears to be failing to locate or execute
crush.exe .

I am running on Crush version (unknown) as I am unable to query my version using the available
tools.

[caarlos0]

I believe the problem might be your alias - maybe you cd into the folder the binary is at?

You should probably simply add crush.exe to some folder in your PATH, and it should be available everywhere.

Crush will create the .crush folder at the current working directory - if you really wish to change that, you can create a crush.json with the following:

{
  "$schema": "https://charm.land/crush.json",
  "options": {
    "data_directory": "another data directory"
  }
}

But I believe the easier fix is to have it in your PATH et al.