Re: another problem with bash PS1 handling

[Nils]

On 19 Okt., 02:56, Chet Ramey <chet.ra...@case.edu> wrote:
> Second, there are a couple of problems with Posix and this construct.
> You can make an argument that Posix doesn't apply, since it only
> calls for parameter expansion on the value of PS1, and that does not
> include command substitution.  Even if it does apply, it's not clear
> whether or not the expansion of ! to the history number should be
> performed before or after the word expansions.  Bash chooses to do it
> before the expansion, since that's when it's scanning the string for
> the other backslash-prefixed expansions it performs, and it looks like
> ksh does it after the word expansions.

Whether POSIX applies or not, from a logical standpoint history number
and custom bash escape expansion should be last, after parameter
expansion and command substitution because doing it first breaks
command substitution (see my earlier post) or using variables in a
prompt (a='!'; PS1='$a ' will result in a literal "!" rather than the
history number), it is unintuitive and deviates from the behavior of
other shells such as variants of ash and ksh.