Functions called in opposite order in midnight commander subshell about bash-preexec HOT 2 CLOSED

bash-preexec doesn't support the case where PROMPT_COMMAND is modified after the shell startup and the first prompt. However, Midnight Commander installs its hook by directly inputting PROMPT_COMMAND+=..., etc. as user commands from stdin after starting the shell.

More specifically, bash-preexec requires that all the other PROMPT_COMMAND hooks are enclosed between __bp_precmd_invoke_cmd and __bp_interactive_mode. This is normally achieved through the initial DEBUG trap (__bp_install) installed by bash-preexec. However, Midnight Commander injects codes after the shell startup and modifies PROMPT_COMMAND. This results in the following value of PROMPT_COMMAND:

$ declare -p PROMPT_COMMAND
declare -- PROMPT_COMMAND=$'__bp_precmd_invoke_cmd\n__bp_interactive_mode\npwd>&11;kill -STOP $$'

The substring pwd>&11;kill -STOP $$ is the hook installed by mc. We can see that the mc hook string is not enclosed within __bp_precmd_invoke_cmd and __bp_interactive_mode. Instead, this should look like the following:

PROMPT_COMMAND=$'__bp_precmd_invoke_cmd\npwd>&11;kill -STOP $$\n__bp_interactive_mode'

I'm not sure if there is a solution at the user side.

from bash-preexec.

Thanks, this info is enough for me.

After patching subshell/common.c in the mc sources it works like a charm!

--- common.c    2023-03-06 13:14:44.536493089 +0100
+++ common.c.patched    2023-03-06 13:13:51.448906309 +0100
@@ -825,7 +825,7 @@
     {
     case SHELL_BASH:
         g_snprintf (precmd, buff_size,
-                    " PROMPT_COMMAND=${PROMPT_COMMAND:+$PROMPT_COMMAND\n}'pwd>&%d;kill -STOP $$'\n"
+                    " PROMPT_COMMAND='__bp_precmd_invoke_cmd\npwd>&%d;kill -STOP $$\n__bp_interactive_mode'\n"
                     "PS1='\\u@\\h:\\w\\$ '\n", subshell_pipe[WRITE]);
         break;

from bash-preexec.