Subject: Re: bug#1849: Windows 7 Taskbar Support

From: Lars Ingebrigtsen <[email-masked]>
Date: Mon, 29 Feb 2016 15:20:15 +1100

"Michael Kleehammer" <[email-masked]> writes:

> To work well with the upcoming Windows 7, the Windows version of emacs will need
> to start from emacs.exe without allocating the extra console window.  This means
> it will need to be linked as a GUI program instead of a console program.

[...]

Jason Rumney <[email-masked]> writes:

> Reopened.
>
> It seems that this is only partially done.  Emacs, emacsclient and
> runemacs are setting the AppUserModel ID consistently, so when running
> their windows will group together. But there are two remaining changes
> before this can be considered complete:
>
> 1. Set the AppUserModel ID on the shortcut created by addpm.exe, so
> dragging the shortcut to the taskbar will work as expected (pinned
> shortcut grouped with windows of running emacs).
>
> 2. Set the AppUserModel RelaunchCommand property of Emacs windows to
> "runemacs.exe" so that pinning an running Emacs instance works as expected
> (launch via runemacs.exe so the command window does not show).
>
> Unfortunately both of these require directly using the IPropertyStore
> interface, which is only available on Windows versions since Vista, and
> is missing from current mingw32 headers, so a significant amount of
> reverse engineering system headers will be involved.

This was four years ago.  Has this been fixed in the meantime?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no