Re: Bash Prompt Here opening in Windows Console/Terminal on chere 1.4-3

Greetings Vadim,

On 4/12/2026 9:59 PM, Vadim (vadcx) wrote:
> On 4/13/26 03:45, Philippe Cloutier wrote:
>> 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:
> Hi, I'm glad you've found this useful.
>
> I don't exactly understand the issue you have, would you paraphrase it
> in a clearer "expected/actual" way?


I expected that upgrading from 1.4-1 to 1.4-3 would help, but it did 
not, even after I performed the 2 attempts to "reset" my system (get rid 
of traces from 1.4-1) which I described.

That being said, I am not an expert of chere nor Cygwin, so when I say 
"expected", I could also write "hoped". I did not read the code.


>
> All I know, Windows 11 changed its standard console host application.


Yes, I understand that.


> […]
> For debugging, I suggest to compare what the link in Start Menu actually
> calls vs the arguments of the proccess (process tree) started as can be
> seen in Process Explorer (or Process Hacker).

Note that System Informer (which basically replaces Process Hacker) can 
do this just fine.

Sorry, I wanted to report but I am too busy to debug further. All I can 
say is that the output I provided is representative of what happens. 
Everything tells me the registry didn't improve since 1.4-1. It seems 
“stuck” there. "C:\cygwin64\bin\bash.exe" -c "/bin/xhere /bin/bash.exe 
'C:\Users\cheal\Downloads'"

One thing I did not try is to uninstall the chere package. Let me know 
too if Cygwin has a purge command I should try too.