Re: Problems with mintty jump list
- Date: Sun, 1 Jul 2018 15:58:56 +0200
- From: Thomas Wolff <towo@xxxxxxxx>
- Subject: Re: Problems with mintty jump list
Am 13.05.2018 um 23:05 schrieb Michael Schaap:
There does not seem to be a way to determine anything like an inherited
AppID when run from a jump list.
This makes things unnecessarily complicated. I'm adding the following to
the manual page as a note to option TaskCommands:
On 13 May 18 22:04, Thomas Wolff wrote:
Probably, yes. In fact, not just jumplist-started instances, but any
instance (also the default one) opened from the task bar icon.
Thanks, maybe jumplist-started instances should implicitly inherit AppID.
Are you sure --store-taskbar-properties is needed to get the jumplist
stable? This would have additional implications, to be checked.
No, I'm not sure at all. I just added this because the man page told
me for AppLaunchCmd: "This is only effective if combined with an
AppName option and the command-line option --store-taskbar-properties
to make it persistent.". And I *did* have to add an AppLaunchCmd to
the .minttyrc, otherwise the default task bar icon action would open a
window without the AppID, but also without a login shell.
Note: To make the jump list persistent, it is necessary to carefully
apply additional tricks to satisfy the insane taskbar configuration
paradigm of Windows.
First, also configure a default taskbar icon command using options
AppName and AppLaunchCmd.
Second, choose a unique value for AppID and also add it to the (default)
launch command and all (jumplist) task commands.
Third, invoke mintty with the chosen AppID and option
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple