Nigel Horne wrote:
> Since compilation failed bashbug hasn't been installed, so I am having to
> guess what is wanted. Let me know if you need any more help.
Does isinf appear in libc on AIX 5.1? How about isnan?
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere e
[EMAIL PROTECTED] wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i386
> OS: linux-gnu
> Compiler: gcc-34
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-unknown-linux-gnu'
> -DCONF_VENDOR='un
> Try echo "$e". Then read about Word Splitting in the Bash manual.
Good point. Since no word splitting occurs within "$e", it is
expanded to a string containing newlines:
$ echo $e # Expansion without quotes -> word splitting
x sub: f
$ echo "$e" # Expansion with quotes -> no word splittin
While hunting a bug in my script, I stumbled over an effect involving
the usage of
backquote and grep, which completely puzzles me. To reproduce the
effect, execute
first the following four commands, which create a small directory tree
in your
working directory and set the bash variable 'e':
On Fri, Mar 03, 2006 at 11:10:50AM -0500, Chet Ramey wrote:
> Bash-Release: 3.1
> Patch-ID: bash31-010
> [...]
> THIS IS AN UPDATED PATCH. [...]
Uh. Why couldn't you just release a new patch on top of the old ones
instead? Would have been less cumbersomely for build systems where the
source an
"Com MN PG P E B Consultant 3" <[EMAIL PROTECTED]> writes:
> (1) yank 0th arg, similar to yank-last-arg, but copies the command part
> of the previous line
> into the current buffer. Example: The previous line was
>
> /usr/local/bin/perl myprog.pl
>
> then yank-0th-arg should insert /usr/local/b
I would find the following two functions useful in bash command line
editing; is it possible
to simulate them somehow with the current bash version, or would this
have to be a new feature
in a future version of bash?
(1) yank 0th arg, similar to yank-last-arg, but copies the command part
of the pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 3/14/2006 4:26 AM:
>
> Bash Version: 2.05b
> Patch Level: 0
Consider upgrading. Bash is now at 3.1 patch level 14. Perhaps your
problem has already been identified and fixed in subsequent releases.
- --
Life is sh
Linda W <[EMAIL PROTECTED]> writes:
> I believe bash is broken in regards to using "any" number after
> "\" as an octal value. The shell specifications require the leading
> zero for an octal constant
The specification does not _require_ it, it allows it. Any other use of
the backslash results
Mihai Barbos <[EMAIL PROTECTED]> writes:
> When IFS is "\n" a single n at the end of a line is dropped.
IFS="\n"
is equivalent to
IFS=n
If you want to set IFS to a single newline character use either
IFS=$'\n'
or
IFS="
"
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux
tis 2006-03-21 klockan 17:32 +0100 skrev Ralf Wildenhues:
> To finish this up for squid: Please install the patches below (it'd be
> nice if you could feed back the cppunit related ones to their upstream),
> install the file lib/cppunit-1.10.0/config/ax_prefix_config_h.m4 from
> http://autoconf-a
* Ralf Wildenhues wrote on Tue, Mar 21, 2006 at 05:02:49PM CET:
>
> The issue is not in Autoconf, but in the macro AC_CREATE_PREFIX_CONFIG_H
[...]
> I will look into that, and post an update.
To finish this up for squid: Please install the patches below (it'd be
nice if you could feed back the c
Henrik Nordstrom wrote:
fre 2006-03-17 klockan 19:31 -0800 skrev Linda W:
Mystery solved.
My shell _expanded_ control sequences by default in echo. (echo "\1" -> becomes
"echo ^A").
Apparently there are literals in the configure script like "\\1" "\\2" that
were trying to echo a literal '\1'
lör 2006-03-18 klockan 14:15 -0800 skrev Linda W:
> Bash added the "feature" to allow dropping of the leading
> "0", accepting strings: "\0nnn", "\nnn", and "\xHH". I'm guessing that
> most bash users run in a shell that has expansion turned off by default or
> this would have come up befo
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: linux-gnu
Compiler: gcc-34
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DSHELL -DHAVE_CONFIG_H -I. -I
sön 2006-03-19 klockan 12:57 -0800 skrev Paul Eggert:
> Autoconf deals with shells that do not conform to XSI, and where the
> results are implementation-defined if there's a backslash anywhere in
> the string, so to some extent this point is moot for Autoconf (though
> it's undeniably a portabili
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='b
Hello,
I just found a bug that affects a number of shells
(pressumably the
code there is from the same roots) in the parser.
The following code;
l='eval "$l"'
eval "$l"
Which sets off an infinite recursion on 'eval', should
result in an
infinite loop to be terminated by INT (doesnt' work)
or
Henrik Nordstrom wrote:
lör 2006-03-18 klockan 14:15 -0800 skrev Linda W:
Bash added the "feature" to allow dropping of the leading
"0", accepting strings: "\0nnn", "\nnn", and "\xHH". I'm guessing that
most bash users run in a shell that has expansion turned off by default or
this wo
Since compilation failed bashbug hasn't been installed, so I am having to
guess what is wanted. Let me know if you need any more help.
uname -a: AIX marvin 1 5 005A0E6C4C00
cc version: C for AIX Compiler, Version 6
CFLAGS=-O2 ./configure works fine
make fails thus:
...
cc -c -DHAVE_CONFIG_H -
* Chet Ramey <[EMAIL PROTECTED]> [2006-03-05 12:38 -0500]:
> This has been a known issue with bison-1.75 for over three years:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=167635;archive=yes
> http://lists.gnu.org/archive/html/bug-bash/2003-01/msg00061.html
> http://lists.gnu.org/archive/h
Retrying as this mail does not appear after 5 days
Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-mandriva-linux-gnu'
-DCONF_V
* Ralf Wildenhues wrote on Tue, Mar 21, 2006 at 05:02:49PM CET:
> FWIW, are there _any_ other shells that do not output \1 with
> echo "\\1"
> except for bash-3.0-with-xpg-echo?
Ouch. Never mind that stupid question, please.
___
Bug-bash mailing lis
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale'
-DPACKAGE
Hi folks.
Currently, the documentation (both, help-command and manpage) on
ulimit -f says:
"The maximum size of files created by the shell"
which may make one think of, it only affects files that are created
from the shell itself.
Assuming -f works like it should work, a text like:
"The maxi
25 matches
Mail list logo
