TSlivede

Thanks for creating an explicit issue for this! Alternative suggestion regarding the removal of "Insignificant leading and trailing whitespace": How about considering only a maximum of one leading space and...

> people may be more used to any number of leading/trailing spaces being are insignificant Yes you are right, the syntax I suggested might be very surprising to new users,...

Another alternative idea: Allow only a maximum of three quotes in the delimiters and don't remove leading/trailing whitespace. This way we would lose the visual advantage > - It makes...

Addition to that suggestion: To allow embedding literal `'''@` maybe allow multiple (unlimited?) `@` symbols in the string delimiters. E.g.: ``` @@'some string containing >>>'@

Oh, just as a note: gpaste works again after removing the huge amount of unnecessary entries from the history file with vim.

I now have a workaround: I manually set the uninitialized scaling properties by hand. This is most certainly not the intended way, but it works. To do this I copied...

Tested with git-for-windows version 2.25.0.windows.1 and wslbridge-0.2.4-cygwin64: C:\Users\username>echo %HOME% %HOME% so HOME is not set in my global environment C:\Users\username>D:\Programs\Git\bin\git.exe config --global -e has opened C:/Users/username/.gitconfig C:\Users\username>D:\ExcludeFromBackup\tmp\wslbridge-0.2.4-cygwin64\wslbridge.exe User@hostname:/mnt/c/Users/username$ echo $HOME...

@zviryatko The problem with `export WSLENV=HOME/p` is that the Windows `HOME` variable then points to the WSL directory, so git for Windows is then using the `.gitconfig` of you WSL...

I don't know if the behavior of scenario F should be changed. This is simply the behavior of cmd.exe. To make it work just use ``` cmd.exe /c@ 'C:\Program Files\PowerShell\7-preview\pwsh'...

I agree, that `cmd /c ""` must not be broken. But wouldn't it be enough to provide a function similar to ``` function Invoke-Cmd() { $PSNativeCommandArgumentPassing='Legacy'; & $Env:ComSpec @args }...