>I tried setting ENABLE_VIRTUAL_TERMINAL_PROCESSING right at the early stages of ./mach being invoked As far as I can tell, this flag is initially already set. What's super weird is that it becomes unset during [`get_base_mozconfig_info()`](https://searchfox.org/mozilla-central/rev/0a2eba79c24300ce0539f91c1bebac2e75264e58/python/mozbuild/mozbuild/base.py#331), specifically during `sandbox._value_for(sandbox["mozconfig_options"])`. For some reason the flag remains set and then is already unset at the first line of [`mozconfig_options()`](https://searchfox.org/mozilla-central/rev/0a2eba79c24300ce0539f91c1bebac2e75264e58/build/moz.configure/init.configure#177), and this makes me believe something in the sandbox is manipulating it.
Bug 1744340 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
>I tried setting ENABLE_VIRTUAL_TERMINAL_PROCESSING right at the early stages of ./mach being invoked As far as I can tell, this flag is initially already set. What's super weird is that it becomes unset during [`get_base_mozconfig_info()`](https://searchfox.org/mozilla-central/rev/0a2eba79c24300ce0539f91c1bebac2e75264e58/python/mozbuild/mozbuild/base.py#331), specifically during `sandbox._value_for(sandbox["mozconfig_options"])`. For some reason the flag remains set right before that line and then is already unset at the first line of [`mozconfig_options()`](https://searchfox.org/mozilla-central/rev/0a2eba79c24300ce0539f91c1bebac2e75264e58/build/moz.configure/init.configure#177), and this makes me believe something in the sandbox is manipulating it.