unsetting from BASH_ALIASES

2015-10-26 Thread isabella parakiss
man bash claims that unsetting elements from BASH_ALIASES causes them to be removed from the alias list. This doesn't work and from what I can see in variables.c there's nothing that's called when an element in a dynamic variable is unset. Is there any plan to support this? --- xoxo iza

Re: bashdb sig-test.sh failure

2015-10-26 Thread Rocky Bernstein
No failure using 4.4.0(1)-beta (x86_64-unknown-linux-gnu). Thanks. I'll adjust things on my side then. On Mon, Oct 26, 2015 at 2:00 PM, Chet Ramey wrote: > On 10/26/15 1:25 PM, Rocky Bernstein wrote: > > > Bash Version: 4.3 > > Patch Level: 11 > > Release Status: release > > > > Description:

Re: Bug in !! expansion, bash 4.4-beta

2015-10-26 Thread Chet Ramey
On 10/25/15 5:49 PM, Keith Thompson wrote: > I'm running bash 4.4 beta, built from source (bash-4.4-beta.tar.gz) on > Linux Mint 17.2. > > !! history expansion works correctly in simple cases, but not when part of > a $(...) expansion. > > This problem does not occur with bash 4.3.11 > > The las

Re: bashdb sig-test.sh failure

2015-10-26 Thread Chet Ramey
On 10/26/15 1:25 PM, Rocky Bernstein wrote: > Bash Version: 4.3 > Patch Level: 11 > Release Status: release > > Description: > > Weird trap debug and signal handling problem in bashdb in running test > test/integration/test-sig..sh. I've tried to narrow to scope of the problem > by reduc

SIGSTOP and bash's time built-in

2015-10-26 Thread Stefan Tauner
Hi, I was creating some exercises for my students when I noticed very strange behavior of the time built-in when sending SIGSTOP to a timed command interactively (via ^Z): $ time sleep 5 ^Z [1]+ Stopped sleep 5 real0m0.880s user0m0.002s sys 0m0.000s $ ps Tf PID TTY

bashdb sig-test.sh failure

2015-10-26 Thread Rocky Bernstein
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE

Re: Bash-4.4-beta available for FTP

2015-10-26 Thread Chet Ramey
On 10/23/15 1:50 PM, Michael Felt wrote: > I do not mind installing yacc :) You would need to install bison anyway. > How about the redefine of mbchar_t ? See my previous reply; AIX is no more entitled to this symbol than anyone else. Bash doesn't actually use this symbol internally, since it o

Re: Bash-4.4-beta available for FTP

2015-10-26 Thread Chet Ramey
On 10/23/15 3:08 AM, aixtools wrote: > On 2015-10-15 16:23, Chet Ramey wrote: >> The first beta release of bash-4.4 is now available with the URL >> >> ftp://ftp.cwru.edu/pub/bash/bash-4.4-beta.tar.gz >> >> This tar file includes the formatted documentation (you should be able to >> generate update

Re: Bugs in bash-4.4-beta running on OpenBSD

2015-10-26 Thread Eduardo A . Bustamante López
On Mon, Oct 26, 2015 at 09:02:21AM -0400, Chet Ramey wrote: > Use bison. Command substitution requires invoking the parser recursively, > and byacc is completely incapable of reentrant parsing. > > This is one of the reasons that production bash releases ship with versions > of y.tab.c and y.tab.

Re: PROMPT_COMMAND and PS1 error

2015-10-26 Thread Florian Mayer
Ah thanks! Sadly paragraph https://www.gnu.org/software/bash/manual/bash.html#Command-Substitution doesn't mention this behaviour. Would it be possible to add a line describing this? I know that it's in the manual somewhere else, but maybe you could prevent some unnecessary questions on this mai

Re: Substring expansion error when offset contains a colon

2015-10-26 Thread Chet Ramey
On 10/19/15 3:45 AM, grishale...@gmail.com wrote: > When using ${parameter:offset:length} expansion, the parser doesn't account > for all the ways that a colon can appear in "offset". > > For example: > > $ echo ${PARAM:${OFFSET:-0}} > -bash: ${OFFSET: bad substitution > > or: > > # declare -A

Re: Bugs in bash-4.4-beta running on OpenBSD

2015-10-26 Thread Chet Ramey
On 10/26/15 8:07 AM, Eduardo A. Bustamante López wrote: > Hi Chet, > > I compiled bash with: > > CFLAGS='-O0 -g' ./configure --silent && make -j2 && make tests 2>&1 | tee > out.log > > And I get many parsing errors in the results. Most seem to be parenthesis > related, and some segfaults. I hop

Re: Design question(s), re: why use of tmp-files or named-pipes(/dev/fd/N) instead of plain pipes?

2015-10-26 Thread Greg Wooledge
On Fri, Oct 23, 2015 at 04:01:37PM -0600, Bob Proulx wrote: > The /proc/self/fd/ directory is a kernel construct. It does not have > normal file system semantics. > And really what would be a sane purpose in being able to remove files > from it? What would that do? Would that make any sense at

Bugs in bash-4.4-beta running on OpenBSD

2015-10-26 Thread Eduardo A . Bustamante López
Hi Chet, I compiled bash with: CFLAGS='-O0 -g' ./configure --silent && make -j2 && make tests 2>&1 | tee out.log And I get many parsing errors in the results. Most seem to be parenthesis related, and some segfaults. I hope these two lead to fixing the whole thing: $ uname -a OpenBSD openbsd.m