[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

BASH_COMMAND should be set before PS0

From: Taqras
Subject: BASH_COMMAND should be set before PS0
Date: Sat, 19 Mar 2022 18:07:27 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0

Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin:/usr/bin' -DSTANDARD_UTILS_PATH='/usr/bin' -DSYS_BASHRC='/etc/bash.bashrc' -DSYS_BASH_LOGOUT='/etc/bash.bash_logout' -DNON_INTERACTIVE_LOGIN_SHELLS uname output: Linux EliteBook 5.16.15-arch1-1 #1 SMP PREEMPT Thu, 17 Mar 2022 00:30:09 +0000 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu

Bash Version: 5.1
Patch Level: 16
Release Status: release

      The value of this parameter is expanded like PS1 and displayed by
      interactive shells after reading a command and before the command is
      The command currently being executed or about to be executed, unless
      the shell is executing a command as the result of a trap, in which
      case it is the command executing at the time of the trap. If
      BASH_COMMAND is unset, it loses its special properties,
      even if it is subsequently reset.
      By the time PS0 is displayed, BASH_COMMAND is still set to the
      previous command, not the command about to be executed.

      And that's just about the only problem:
      Thank you very much for your good work!!!


    Assign BASH_COMMAND before expanding PS0

reply via email to

[Prev in Thread] Current Thread [Next in Thread]