|
From: Kevin W. <kw...@co...> - 2025-10-21 12:33:58
|
Checking for the existence of the check_screenreader command via "info commands" allowed a child interp to load cleanly. I did not see a failure on this issue in the test suite, so I've committed the update with the expectation that the test suite will now pass. This also appears to mean that accessibility cannot run in a child interp, because the absence of the command check_screenreader command means accessibility will not load. Is that a problem? I'm fine documenting it in the TIP and/or man page. Please advise. On 10/21/25 7:47 AM, Kevin Walzer wrote: > This is an area I don't really work with, so I don't understand what > is going on. Why wouldn't a command that is available in the main > interp fail to be available in a child interp that was not called with > the -safe flag? I understand there's probably some machinery here I'm > not wiring up - any suggestions? |