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

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?

All I know, Windows 11 changed its standard console host application.
This is my best guess why the behavior is different. I tested on Windows
10 only and some stuff was purely trial & error (icons in particular).

I do not have the ability to spin up VMs for testing atm, though I'm
generally interested in further work on it.

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).

-- 
Cheers,
Vadim