chaining custom command issue on Windows

[KevinNitroG]

Describe the bug

While defining a custom command keybindings with a chaining command, it failed to run on Windows using cmd shell.

To Reproduce
Steps to reproduce the behavior:

1. Config custom command keybindings in ~/AppData\Roaming\lazygit\config.yml

    customCommands:
     - key: 'G'
       context: 'global'
       command: 'git reflog expire --all --expire=now && git gc --prune=now --aggressive'
       description: 'clean up unnecessary files, reflog, optimize'
       prompts:
         - type: 'confirm'
           title: 'Cleanup'
           body: 'Are you sure you want to unnecessary files, reflog, optimize the repo?'
       loadingText: 'Cleaning up'
       stream: true

2. Go to a repo and run G key in lazygit

Expected behavior

The command run successfully

Screenshots

Version info:

commit=611fabde11d24d9acc71ee26077b9a1101f59f27, build date=2024-09-18T10:56:10Z, build source=binaryRelease, version=0.44.1, os=windows, arch=amd64, git version=2.47.0.windows.2

[stefanhaller]

The reason for this is that lazygit escapes the & characters, turning them into ^&. I'm not sure why it does that, or if we can simply remove it. @jesseduffield Do you remember?

[KevinNitroG]

The reason for this is that lazygit escapes the & characters, turning them into ^&. I'm not sure why it does that, or if we can simply remove it. @jesseduffield Do you remember?

when I run the command (contains "^&^&") it still works. Maybe that's not the cause

[jesseduffield]

The reason for this is that lazygit escapes the & characters, turning them into ^&. I'm not sure why it does that, or if we can simply remove it. @jesseduffield Do you remember?

I do not remember, but perhaps this has something to do with the fact that we previously quoted all commands, meaning we could do without the escaping now. But I'm not well versed on what we need to do for windows