Path: csiph.com!usenet.pasdenom.info!news.redatomik.org!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!news.tele.dk!news.tele.dk!small.news.tele.dk!usenet.stanford.edu!not-for-mail
From: isabella parakiss <izaberina@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: ! in PS1 in posix mode
Date: Sun, 11 Oct 2015 08:22:32 +0200
Lines: 27
Approved: bug-bash@gnu.org
Message-ID: <mailman.79.1444544572.7904.bug-bash@gnu.org>
References: <CAAZkfoLdwArFQ4_jB5uL9M+Tr8Kv69XbeJiFw3_NS3HPb=4LSQ@mail.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
To: bug-bash <bug-bash@gnu.org>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <CAAZkfoLdwArFQ4_jB5uL9M+Tr8Kv69XbeJiFw3_NS3HPb=4LSQ@mail.gmail.com>
Precedence: list
Xref: csiph.com gnu.bash.bug:11613

On 10/11/15, isabella parakiss <izaberina@gmail.com> wrote:
> In posix mode, bash replaces ! in my PS1 with the history number.
>
> $ PS1=' ! '
>  ! set -o posix
>  513 exit
>
> It doesn't happen with any other prompt escape sequence, afaict.
> This looks... intentional?  WTF?
>

Ok I've now read this page: http://tiswww.case.edu/php/chet/bash/POSIX
This is awful.

I found out this by enabling set -o posix in my interactive shell.  bash
replied with an endless loop of syntax errors because there's this in my
PS1:  ${var[a != b]}
Then bash decided to eat up as much cpu and memory it could grab, and I
had to kill-9 it.

I understand that changing the standard in unfeasible but a syntax error
in PS1 shouldn't destroy the shell.


---
xoxo iza