Aw: Re: Re: Bash different behaviour of read / strings in jessie versus stretch (regression?) [SOLVED]

e versus stretch (regression?) On Tue, Jan 10, 2017 at 01:10:53AM +0100, foo fighter wrote: > mapfile -t _array <<<"${_inputstring// /$'\n'}" For larger inputs, this will probably be more efficient: mapfile -t _array < <(your command | tr ' ' '\n') Bash's substitution can be rather slow on large strings.  

Aw: Re: Bash different behaviour of read / strings in jessie versus stretch (regression?)

Hi Greg,   thanks for your answer. I used "read" because it offered different delimiter (IFS) at the same time as far as my elements are seperateed by LF or (one) space (per element). You are right it is stdout of other programs. Furthermore globbing was not intended in this area but I did not

Aw: Bash different behaviour of read / strings in jessie versus stretch (regression?)

Hi, there is further different behaviour (error exit in jessie, no exit in stretch), I posted in debian-devel. https://lists.debian.org/debian-devel/2017/01/msg00331.html Yours lopiuh

Bash different behaviour of read / strings in jessie versus stretch (regression?)

Hi,   the same code behaves different in jessie and stretch. Does someone know why, and if this could be a regression? In jessie "version 1" and "version 2" behave identical. In stretch, "version 2" behaves different (only one item in array) The code difference between "version 1" and "version

this is a test message

It should work as ETRN command : Sorry for unconvinience... q.

crossover install?

I currently am using RedHat and would like to try out debian 1.3. My problem is that I currently have no working floppy. I grabbed the base packages from ftp.debian.org(not the disk images). How should I go about this? I have a formatted ext2 partition already prepared, can I run dpkg with a