[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [h-e-w] Fwd: Windows 10 Taskbar Behavior

From: Eli Zaretskii
Subject: Re: [h-e-w] Fwd: Windows 10 Taskbar Behavior
Date: Sat, 17 Oct 2015 14:17:24 +0300

> Date: Thu, 15 Oct 2015 23:09:27 -0400
> From: Rob Davenport <address@hidden>
> Cc: Eli Zaretskii <address@hidden>, "address@hidden" <address@hidden>, 
>       "address@hidden" <address@hidden>
> Now on my Windows 10 laptop, I'm not seeing David's original problem. I can 
> pin
> Emacs after running it from runemacs.exe and run multiple instances and they
> are grouped on the taskbar as desired. i checked and the shortcut does not 
> have
> an AppID, but things are working as desired. 
> I added the AppID to the shortcut in my Start Menu folder, started Emacs using
> it, pinned it to the taskbar, and the shortcut *does* have the "GNU.Emacs"
> AppID and things work as desired. 
> So now I'm not sure what's going on. I've gotten it to work on Win7, Win8, and
> Win10. And maybe on this Win10 laptop things have gotten messed up. I may have
> to create plain VMs without Emacs every having been installed/run and then 
> test
> things. But for now, it seems it *can* be made to work on all three OS's, 
> maybe
> having to set the AppID in a shortcut.

So you are saying that if the shortcut in Start Menu doesn't have the
AppID, then Emacs started from that shortcut will not be able to be
pinned correctly, i.e. the pinned taskbar shortcut will not have the
AppID property?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]