Re: Fwd: Windows 10 Taskbar Behavior

> From: Rob Davenport <[email protected]>
> CC: "[email protected]" <[email protected]>,
> 	"[email protected]" <[email protected]>
> Date: Thu, 15 Oct 2015 19:45:19 +0000
> 
> <time passes...>
> I have now tried it on a Windows 8 machine.  I started Emacs via runemacs.exe, pinned it to the taskbar and the shortcut *does* have the AppID.
> I tried running emacs.exe.   Got two windows as expected.   When I tried pinning the console window emacs.exe, the shortcut did *not* have the AppID.
> When I tried pinning the GUI windows of Emacs.exe, the shortcut *did* have the AppID.
> 
> On Windows 7, I used procmon and watched what files and registry entries are hit when pinning.  Noticed that the Emacs.lnk under the Start Menu\Programs\Gnu Emacs\ folder was getting queried.  I checked *that* link and sure enough, it did *not* have any AppID.  Hmm.   I tried giving it a test AppID of "MyAppID" - then, launched Emacs via that shortcut and pinned it.  I got another taskbar icon, in addition to the running Emacs, but no AppID.  Then I gave the StartMenu Emacs.lnk the 'GNU.Emacs' AppID, launched and pinned it.  Now the taskbar shortcut *has* the GNU.Emacs AppID.     So it can work on Windows 7 for me.  

Sorry, I got lost here somewhere.  What does the Start Menu have to do
with this issue?

> I typically launch Emacs via a command prompt alias - not the Start Menu.  (How do you normally start Emacs?  Start Menu shortcut, or some other means?)  I suspect that might be the difference in our experience in what lnks get the AppID in various OS's.

I start Emacs from a desktop icon that invokes runemacs.exe.

> The addpm program will create the Start Menu shortcut, but I don't see code in there that would set the AppID.  Perhaps it should?

I never use addpm.  Why do you use it?