Returned due to virus; was:Mail Delivery (failure [EMAIL PROTECTED])

2005-02-17 Thread bug-bash
information. File name: message.scr Virus name: W32/[EMAIL PROTECTED] Copyright © 1993-2003, Networks Associates Technology, Inc. All Rights Reserved. http://www.mcafeeb2b.com ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo

Returned due to virus; was:Mail Delivery failure ([EMAIL PROTECTED])

2005-03-27 Thread bug-bash
information. File name: message.pif Virus name: W32/[EMAIL PROTECTED] Copyright © 1993-2003, Networks Associates Technology, Inc. All Rights Reserved. http://www.mcafeeb2b.com ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo

(no subject)

2005-05-07 Thread bug-bash
___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

bash doesn't compile when configured with --disable-bang-history

2005-06-07 Thread bug-bash
ns for BANG_HISTORY in variables.h and variables.c in a sensible way _______ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

building: recutils bash builtins/readrec.so; ./configure --with-bash-headers=... # fails

2017-11-03 Thread bug-bash
No response today from bug-recutils: http://lists.gnu.org/archive/html/bug-recutils/2017-11/msg4.html For the ./configure, I untarred the latest bash source into a subdir, and set --with-bash-headers= to that pathname. Perhaps someone with an understanding of GNU configure/autoconf etc

bash 1-liner or function to tee to STDERR in middle of pipe?

2020-07-03 Thread bug-bash
This does what I want: --8<---cut here---start->8--- _tee_stderr () { <<'eohd' SYNOPSIS ourname DESCRIPTION Use in a pipe. Leaks STDIN to STDERR. Passes STDIN to STDOUT unchanged. EXAMPLE $ seq 5 |_tee_stderr

Re: foo | tee /dev/stderr | bar # << thanks!

2020-07-04 Thread bug-bash
Hi Lawrence: On Fri 7/3/20 14:03 -0400 =?utf-8?Q?Lawrence_Vel=C3=A1zquez?= wrote: >What's wrong with `foo | tee /dev/stderr | bar`? Perfect! This morning I had thought of foo | tee >(cat >&2) | bar but your soln is simplier. I assume /dev/stderr is on non linux UNIX also. -- thanks-you!,

RE: Double quotes do not work in command substitution?

2007-07-03 Thread neitsch+bug-bash
scripts with 'set -xv' is helpful in figuring out this sort of thing. ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Operator || disables set -e in subshells: Bug or feature?

2008-05-19 Thread bug-bash-reply
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' -DPACKA

file access time and file modification time

2019-07-08 Thread mjbaars1977.bug-bash
Hi,I'm having some difficulties with the file access time and the file modification time. Scripts are attached for your convenience.Regards,Mischa Baars.Sent from my Samsung Galaxy smartphone. conditional.sh Description: application/sh accesstime.sh Description: application/sh

${VAR:4@Q} parameter modifiers don't compose

2020-09-21 Thread d+bug-bash
Variable transforms such as ${VAR@Q} do not compose with substrings expansions, eg ${VAR:1:4}. For example, I expected ${VAR:4@Q} to quote ${VAR:4}, but instead: -bash: VAR: 4@Q: value too great for base (error token is "4@Q") This is because parameter value modifiers do not compose; gen

[patch] mkinitcpio segfaults sometimes (with bash 'devel', but not with bash 5.0.007)

2019-07-03 Thread howaboutsynergy--- via bug-bash
3:14 CEST 2019 x86_64 GNU/Linux Machine Type: x86_64-pc-linux-gnu Bash Version: 5.0 Patch Level: 7 Release Status: maint all other details got lost when I answered 'n' to: Send bug report to bug-bash@gnu.org? [y/n] (and I don't feel like typing all that again) but all

Suggestion that might help clarify meaning

2019-06-24 Thread Gavin Rebeiro via bug-bash
Hi, I've been searching the BASH manual ( https://www.gnu.org/software/bash/manual/bash.html) to find out about the precedence/sequence that the shell parses commands. The particular question I've had which I was helped with: https://unix.stackexchange.com/questions/526646/precedence-of-subshells-

seg fault after interrupting time of shell function

2019-07-03 Thread Fergus Henderson via bug-bash
bar 2. Interrupt the command in step 1 by hitting control-C after "bar" has been running for a second or two. 3. Type the following commands: bar Terminal log from reproducing this bug: bash$ env - bash --noprofile --norc bash-4.4$ ulimit -c unlimited bash-4.4$ cd /tmp