Jan Lindemann bb13aea694 lib.ExecContext: Fix ignored --interactive ... Whether or not the CallContext.interactive property should be True or False, and hence, a call should be processed interactively, depends on multiple factors, constituting matrix of options with multiple preferences. --interactive is the application default and can be true, false, or auto - A call can be explicitly invoked as interactive, non-interactive or auto via the cmd_input parameter to ExecContext.run() This commit adds more "mode:" options to make the latter more explicit. It takes preference over the global --interactive parameter: Global --interactive is only given a chance to decide if cmd_input is None (default) or mode:opt-interactive. This commit also fixes a bug: --interactive is ignored because the interactive argument passed to ExecContext's constructor is ignored later on in calls to the wrapped _run() and _sudo() methods. Signed-off-by: Jan Lindemann <jan@janware.com>		2026-03-25 07:32:45 +01:00
..
python	lib.ExecContext: Fix ignored --interactive	2026-03-25 07:32:45 +01:00
Makefile	projects.py: Move bulk of code into module	2025-11-15 11:08:52 +01:00