Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #11613 > unrolled thread

Re: ! in PS1 in posix mode

Started byisabella parakiss <izaberina@gmail.com>
First post2015-10-11 08:22 +0200
Last post2015-10-11 08:22 +0200
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: ! in PS1 in posix mode isabella parakiss <izaberina@gmail.com> - 2015-10-11 08:22 +0200

#11613 — Re: ! in PS1 in posix mode

Fromisabella parakiss <izaberina@gmail.com>
Date2015-10-11 08:22 +0200
SubjectRe: ! in PS1 in posix mode
Message-ID<mailman.79.1444544572.7904.bug-bash@gnu.org>
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

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web