Tony, can you Report a Problem on the git line staging - they are monitoring feedback on it.
From: Tony McGee via ozdotnet <ozdotnet@ozdotnet.com> Sent: Monday, August 29, 2022 12:50 PM To: ozdotnet@ozdotnet.com Cc: Tony McGee <tmcgee...@gmail.com> Subject: Re: VS2022 recent list stall Heh, yeah VS2022 search text boxes appear to be a bit wonky occasionally. Tim Corey called it out in a MAUI first look video a few months back when something similar happened in the 17.3 preview bits. I guess it's not fixed yet... https://youtu.be/HmyfjAaPW0g?t=109<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyoutu.be%2FHmyfjAaPW0g%3Ft%3D109&data=05%7C01%7Cdavid.kean%40microsoft.com%7C4ddadcff21464557971e08da896966dd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637973383541159693%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=9FH3DLd5dxaFZ0VNWYGJQ%2FU47DtyGoUERt13UM40X94%3D&reserved=0> Speaking of annoyances with the latest VS2022 - the new git line staging thing is so aggressive with the mouse popup up at the end of a line now, making edits to a diff painful: https://devblogs.microsoft.com/visualstudio/git-line-staging-released/<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdevblogs.microsoft.com%2Fvisualstudio%2Fgit-line-staging-released%2F&data=05%7C01%7Cdavid.kean%40microsoft.com%7C4ddadcff21464557971e08da896966dd%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637973383541159693%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=Ysdiz86YftzsxLqsSSZaMYKj3QzhYjRn7VMVQA0DT7A%3D&reserved=0> On 29/08/2022 12:20, Greg Keogh via ozdotnet wrote: Has anyone else got a problem with the Open recent list in the latest VS2022? Type some search text and it just stalls busy with empty results. [cid:image001.png@01D8BC60.0419ED80] I've also noticed that the Replace in Files feature over external folders has the same bug I reported several weeks ago. It will tell you "x occurrences(s) replaced" but no files are touched. I reported this back then, but a support person noticed a duplicate posted after me, so I got marked as a duplicate (but I was first!!). I would have thought that this was a really serious issue, but it seems to have gone quiet. Doesn't anyone else use VS for global changes? It's a powerful feature. Greg
