Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
OCGV: Move "Set cursor key to application mode" fix to gui.cs
See original GitHub issueI think this may be a bug that impacts all gui.cs apps and should be fixed there. However, I don’t fully understand what the user impact of the bug described in these comments was and how setting the cursor key to application mode fixed it. Can you provide more detail?
As an aside, IIRC, Dispose for a Cmdlet is not actually guaranteed to get called until the CmdLet’s module is unloaded. And that does NOT happen immediately after the Cmdlet is run. This Dispose gets called in OutConsoleGridviewCmdletCommand’s Dispose. In building out-winprint I discovered that I could not count on Dispose for timely cleanup and instead had to do stuff at the end of EndProcessing. This is another reason I think this logic should be moved to gui.cs (unless I’m wrong about the fact the underlying bug impacts all gui.cs apps).
Issue Analytics
- State:
- Created 3 years ago
- Comments:19 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Yeah I can’t repro anymore. That’s interesting.
Thanks. I actually use that (and WSL) here and there. The real problem is my dev skillz are barely adequate on Windows, and just getting started being able to enlist and build
GraphicalToolson Linux is a bit much for me right now. I’m capable, it’s just time.