WinGup update waiting...
-
Hi @donho
I see that winGup project has a new commit that is not yet integrated to the NPP releases.
https://github.com/notepad-plus-plus/wingup/pull/48Could you probably plan for an update?
/BR Mattes -
@mattesh ,
Don doesn’t read “General Discussion” threads. If it’s not a reply to one of his Announcements, he’s not likely to see it anywhere in the Forum, despite your @-mention.
According to the PR you linked, it was pulled into the wingup repo, so that repo is up-to-date.
If you can show that the most recent wingup isn’t available in the current v8.6.3-ReleaseCandidate, you should post a reply in that Release Candidate thread, and maybe he’ll update the wingup that he bundles before making the final v8.6.3 release.
----
Update: now that I look, I see he incorporated the PR on Nov 21, which was after the most recent tag in the wingup. So yes, he would have to create a new tag for wingup and incorporate it into the v8.6.3. I think you should reply to the Announcement to v8.6.3-ReleaseCandidate and ask if he can tag wingup to include the most-recent wingup master with fix #48, and then use that wingup when creating the final v8.6.3. Given that he’s in release-candidate mode, I don’t know how willing he will be to bring in the wingup change at the last minute, but it wouldn’t hurt to ask. -
@PeterJones
thanks! I’ll put it there little later; meanwhile seems that this fix might even not be enough for some use cases. I’m testing a bit more before promoting the commit.
Mattes -
@mattesh ,
I’ll put it there little later
I actually already pointed it out to Don here, and he has tagged wingup 5.2.8. He has incorporated that new wingup into Notepad++ v8.6.3-RC2
seems that this fix might even not be enough for some use cases
If you find a use case that isn’t covered by wingup 5.2.8, you will have to create a new wingup issue. A fix for a new issue (likely) won’t make it into the final Notepad++ v8.6.3 release, but it should make it eventually (assuming he is able to come up with a fix).
