> > Using bash-4.4.18
> > Intel core i7 laptop running 32-bit or 64-bit linux Using gcc-8.2.0
> >
> > The configure script does not find libncursesw on a system where
> > only the wide version of ncurses exists - even when readine is linked
> > against ncursesw.
> >
> I haven't seen a distro
On 10/31/2018 11:01 PM, Rob Foehl wrote:
Prompted (pun intended) by the recent thread on detecting missing newlines
in command output, I'd had another look at my own version, and discovered
a potential issue with control characters being written as-is in declare
output. Minimal (harmless)
On 11/13/18 10:29 AM, Service wrote:
# ensure that file1 exists and that file2 does not exist
There's your problem. It is inherently ambiguous what timestamp to use
when a file is missing (infinitely new or infinitely old, or always an
error for not existing); bash's -nt picked one way,
On 13.11. 18:29, Service wrote:
# Put the above commands into a script, say check.sh
# Run with: /bin/sh < check.sh
# Or : /bin/sh ./check.sh
# Or : /usr/bin/env ./check.sh
# Output is always not ok:
not_nt
nt
$ cat check.sh
export PATH=""
On Tue, Nov 13, 2018 at 05:29:42PM +0100, Service wrote:
> Repeat-By:
> Under Windows 10, WSL.
Then why did you send this to a debian.org address?
> Start "bash", terminal with shell pops up.
> 2. This does not work:
>
> # Put the above commands into a script, say check.sh
>
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'
On Tue, Nov 13, 2018 at 09:59:51AM -0500, Chet Ramey wrote:
> On 11/13/18 4:28 AM, Christopher Jefferson wrote:
> > Consider the following script. While the 3 sleeps are running, both jobs
> > -p and $(jobs -p) will print 3 PIDs. Once the 3 children are finished,
> > jobs -p will continue to
On 11/13/18 4:28 AM, Christopher Jefferson wrote:
> Consider the following script. While the 3 sleeps are running, both jobs
> -p and $(jobs -p) will print 3 PIDs. Once the 3 children are finished,
> jobs -p will continue to print the 3 PIDs of the done Children, but
> $(jobs -p) will only
Consider the following script. While the 3 sleeps are running, both jobs
-p and $(jobs -p) will print 3 PIDs. Once the 3 children are finished,
jobs -p will continue to print the 3 PIDs of the done Children, but
$(jobs -p) will only print 1 PID. $(jobs -p) always seems to print at
most 1 PID
