Debian: bash --debugger doesn't start the debugger

2015-10-13 Thread Nicholas Bamber
My investigations indicate that it is still true that as per Debian bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403304) --debugger does NOT start the debugger UNLESS the debugged script has a $1. For example /bin/bash --debugger -- ~/scripts/ex1.sh will just run the script

Re: read and env variables + POSIX => SEGFAULT

2015-10-13 Thread Greg Wooledge
On Mon, Oct 12, 2015 at 04:39:45PM -0700, Linda Walsh wrote: > I wasn't sure if it put the "\n" at the end in a 1-line example. << and <<< always end with a trailing newline. This is 100% unavoidable with that syntax. If your data stream needs NOT to end with a newline, then you have to use < <(

Re: Debian: bash --debugger doesn't start the debugger

2015-10-13 Thread Chet Ramey
On 10/12/15 4:16 PM, Nicholas Bamber wrote: > My investigations indicate that it is still true that as per Debian bug > report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403304) > --debugger does NOT start the debugger UNLESS the debugged script has a $1. We discussed this in a thread on b

Re: command substitution is stripping set -e from options

2015-10-13 Thread Chet Ramey
On 10/13/15 2:04 AM, Christoph Gysin wrote: > On Sat, Oct 10, 2015 at 8:24 PM, Chet Ramey wrote: >> I will consider adding an option to change the behavior of command >> substitution inheriting the -e option, since there doesn't seem to be >> any way to decouple this behavior from posix mode. > >

Re: Want way to run background processes with SIGINT unignored

2015-10-13 Thread Ian Jackson
Ian Jackson writes ("Re: Want way to run background processes with SIGINT unignored"): > Chet Ramey writes ("Re: Want way to run background processes with SIGINT > unignored"): > > This is the behavior that any new option would toggle. Some name like > > `async_sig_ignore' or `async_sig_restore'

Re: Something strange with string replacements

2015-10-13 Thread gaspar . bin
Thanks Greg! You're the best, didn't notice that. I'm testing globasciiranges, it behaves like the C locale and that's very interesting. Thanks again, I really appreciate your explanation. El lunes, 12 de octubre de 2015, 1:33:11 (UTC+2), gaspa...@gmail.com escribió: > Hello, > > I was just t

[PATCH] Provide shopt -s no_async_sig_ignore

2015-10-13 Thread Ian Jackson
This option disables the standards-mandated resetting of SIGINT (and QUIT) to SIG_IGN in asynchronous children. This resetting makes it very hard to write a bash script which invokes a number of subprocesses in parallel and collects the output. The problem is that if you ^C the script, the subpro

bash 4.3.42 configure script needs to test sys/resource.h different on SunOS4

2015-10-13 Thread Klaus Ziegler - owner of sunfreeware.de
Configuration Information [Automatically generated, do not change]: Machine: m68k OS: sunos4.1.1_U1 Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='m68k' -DCONF_OSTYPE='sunos4.1.1_U1' -DCONF_MACHTYPE='m68k-sun-sunos4.1.1_U1' -DCONF_VENDOR='sun' -DLOCALEDIR='/usr/share/local

my confusion on various I/O redirections syntaxes and indirect methods

2015-10-13 Thread Linda Walsh
Chet Ramey wrote: On 10/12/15 7:39 PM, Linda Walsh wrote: Does it also use a tmp file and use process-substitution, or is that only when parens are present? Here-documents and here-strings use temporary files and open them as the standard input (or specified file descriptor) for the command.

Re: my confusion on various I/O redirections syntaxes and indirect methods

2015-10-13 Thread Greg Wooledge
On Tue, Oct 13, 2015 at 01:51:03PM -0700, Linda Walsh wrote: > Well, we have > "<< xxx" > as a HERE DOC using a tmp file Correct. Note that xxx is just the sentinel to tell bash where the here document ends. It's not part of the data. > , Some time ago, the ability to do > "multiple ass