Bash Prompt Here opening in Windows Console/Terminal on chere 1.4-3 (was Re: [PATCH chere 0/4] Overview of chere patches)

Thank you very much for this Vadim

This took me a long time to debug. Just figuring out that my problem was 
specific to Bash Prompt Here took ¼ hour. It would be great to see this 
fixed.

I am no fan of Mintty and am fine with Windows Terminal, but I agree 
Bash Prompt Here should match the Start menu.
The solution looks correct, but I am unfortunately unable to confirm it. 
On the Windows 11 25H2 machine I use which uses the default emulator, I 
see no improvement after the following:

1. Uninstalling, upgrading to 1.4-3 then (re)installing

2. # chere -x

None of the commands fail, but the situation remains unchanged. This is 
not just a lag from File Explorer; I can see the entries removed from 
the registry, then recreated, and restarting does not help.

> $ chere -r
> OS is CYGWIN_NT-10.0-26200
> chere version 1.4
> run.exe is available at C:\cygwin64\bin\run.exe
>
> --- ash keys ---
>
> --- bash keys ---
> Directory menu item (all users)
> &Bash Prompt Here
>
> Directory command (all users)
> C:\cygwin64\bin\bash.exe -c "/bin/xhere /bin/bash.exe '%L'"
>
> Directory background menu item (all users)
> &Bash Prompt Here
>
> Directory background command (all users)
> C:\cygwin64\bin\bash.exe -c "/bin/xhere /bin/bash.exe '%V'"
>
> Drive menu item (all users)
> &Bash Prompt Here
>
> Drive command (all users)
> C:\cygwin64\bin\bash.exe -c "/bin/xhere /bin/bash.exe '%L'"
>
> Drive background menu item (all users)
> &Bash Prompt Here
>
> Drive background command (all users)
> C:\cygwin64\bin\bash.exe -c "/bin/xhere /bin/bash.exe '%V'"
>
> Uninstall description
> Cygwin Bash Prompt Here (x86_64)
>
> Uninstall command
> C:\cygwin64\bin\sh.exe -c "PATH=/bin /bin/chere -u -s bash"
>
>
> --- cmd keys ---
>
> --- dash keys ---
>
> --- fish keys ---
>
> --- mksh keys ---
>
> --- pdksh keys ---
>
> --- posh keys ---
>
> --- tcsh keys ---
>
> --- zsh keys ---
>
> --- passwd keys ---
>

> 3. Consider inclusion in Cygwin installer as a user choice? Then chere
> would need to be way more robust and not just fail on lack of rights
> and an exit code of 0.

It would be great to have chere more discoverable indeed (and not visit 
Stack Exchange to remember how I got Bash Prompt Here every time I 
install Cygwin)!

-- 
🅭🄍:https://www.philippecloutier.com/Common+infrastructure+licensing#list

Philippe Cloutier