> Hi, I had made switch to bash after a decade of tcsh and mostly, I am pleased
> ;-) However there is one particular feature of tcsh which I miss very much
> and that is the ignoration of undescrores or dashes. Just as upper and lower
> case characters are treated the same (when I have "set
> comp
The first release candidate of bash-4.1 is now available with the URL
ftp://ftp.cwru.edu/pub/bash/bash-4.1-rc1.tar.gz
This tar file does not include the formatted documentation (you
should be able to generate it yourself).
This release fixes several outstanding bugs in bash-4.0 and introduces a
The first release candidate of the GNU Readline library, version 6.1,
is now available for FTP with the URL
ftp://ftp.cwru.edu/pub/bash/readline-6.1-rc1.tar.gz
This distribution is essentially a standalone version of the
readline library that appears in Bash-4.1-rc1 together with
an `autoconf' fr
On Tue, Dec 22, 2009 at 08:46:14AM -0500, Chet Ramey wrote:
> The first release candidate of bash-4.1 is now available with the URL
>
> ftp://ftp.cwru.edu/pub/bash/bash-4.1-rc1.tar.gz
The syslog feature (in config-top.h) appears to be enabled by default.
This is quite shocking
On Tuesday 22 December 2009 08:46:14 Chet Ramey wrote:
> The first release candidate of bash-4.1 is now available with the URL
>
> ftp://ftp.cwru.edu/pub/bash/bash-4.1-rc1.tar.gz
also, some implicit decls (some ive posted about in the past):
redir.c:1029: warning: implicit declaration of functio
On Tuesday 22 December 2009 08:46:14 Chet Ramey wrote:
> The first release candidate of bash-4.1 is now available with the URL
top level Makefile.in is missing pathnames.h dependency info for
builtins/evalstring.o and builtins/eval.o.
lib/sh/Makefile.in is still missing a pathnames.h target (see
On Tue, Dec 22, 2009 at 02:23:47PM -0500, Mike Frysinger wrote:
> On Tuesday 22 December 2009 08:46:14 Chet Ramey wrote:
> > The first release candidate of bash-4.1 is now available with the URL
>
> top level Makefile.in is missing pathnames.h dependency info for
> builtins/evalstring.o and built
On 12/22/09 1:44 PM, Greg Wooledge wrote:
> On Tue, Dec 22, 2009 at 08:46:14AM -0500, Chet Ramey wrote:
>> The first release candidate of bash-4.1 is now available with the URL
>>
>> ftp://ftp.cwru.edu/pub/bash/bash-4.1-rc1.tar.gz
>
> The syslog feature (in config-top.h) appears to be enabled by d
On 12/22/09 2:23 PM, Mike Frysinger wrote:
> On Tuesday 22 December 2009 08:46:14 Chet Ramey wrote:
>> The first release candidate of bash-4.1 is now available with the URL
>
> top level Makefile.in is missing pathnames.h dependency info for
> builtins/evalstring.o and builtins/eval.o.
Thanks fo
On Tuesday 22 December 2009 15:49:17 Chet Ramey wrote:
> On 12/22/09 2:23 PM, Mike Frysinger wrote:
> > lib/sh/Makefile.in is still missing a pathnames.h target (see attached
> > patch).
>
> It's never caused a problem for me, and I build with gmake -j N on multiple
> platforms. Odd.
the failure
On 12/22/09 2:39 PM, Mike Frysinger wrote:
> On Tuesday 22 December 2009 08:46:14 Chet Ramey wrote:
>> The first release candidate of bash-4.1 is now available with the URL
>>
>> ftp://ftp.cwru.edu/pub/bash/bash-4.1-rc1.tar.gz
>
> also, some implicit decls (some ive posted about in the past):
>
>
On 12/22/09 3:01 PM, Greg Wooledge wrote:
> On Tue, Dec 22, 2009 at 02:23:47PM -0500, Mike Frysinger wrote:
>> On Tuesday 22 December 2009 08:46:14 Chet Ramey wrote:
>>> The first release candidate of bash-4.1 is now available with the URL
>>
>> top level Makefile.in is missing pathnames.h dependen
On Tuesday 22 December 2009 16:16:51 Chet Ramey wrote:
> On 12/22/09 2:39 PM, Mike Frysinger wrote:
> > shell.c:1726: warning: implicit declaration of function
> > ‘initialize_bashopts’
>
> Interesting, since initialize_bashopts is declared in builtins/common.h,
> and shell.c includes that file.
On 12/22/09 4:28 PM, Mike Frysinger wrote:
> On Tuesday 22 December 2009 16:16:51 Chet Ramey wrote:
>> On 12/22/09 2:39 PM, Mike Frysinger wrote:
>>> shell.c:1726: warning: implicit declaration of function
>>> ‘initialize_bashopts’
>>
>> Interesting, since initialize_bashopts is declared in builtin
Hi all,
I'm not sure if this is a bug or not but it certainly caught me by surprise.
I accidentally created an alias ending with a backslash and a newline today
and the resulting alias proceeded to grab the text on the line _after_ I ran
it. For example:
*$* echo $BASH_VERSION
4.0.33(1)-release
*
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: i686-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/loc
16 matches
Mail list logo