Bash-4.0 Official Patch 44

ut __P((void)); + extern sh_parser_state_t *save_parser_state __P((sh_parser_state_t *)); extern void restore_parser_state __P((sh_parser_state_t *)); *** ../bash-4.0/patchlevel.h2009-01-04 14:32:40.0 -0500 --- patchlevel.h2009-02-22 16:11:31.0 -0500 *** *** 26,30 ***

Bash-4.0 Official Patch 43

case r_reading_string: --- 119,123 case r_reading_until: case r_deblank_reading_until: ! new_redirect->here_doc_eof = redirect->here_doc_eof ? savestring (redirect->here_doc_eof) : 0; /*FALLTHROUGH*/ case r_reading_string: *** ../bash-4.0/patchlevel

Bash-4.0 Official Patch 42

here-document count exceeded")); + reset_parser (); + exit_shell (last_command_exit_value); + } + redir_stack[need_here_doc++] = r; + } + void gather_here_documents () *** ../bash-4.0/patchlevel.h2009-01-04 14:32:40.0 -0500 --- patchlevel.h20

Bash-4.0 Official Patch 41

value) ! : mk_env_string (var->name, value); if (USE_EXPORTSTR == 0) --- 3460,3464 using the cached exportstr... */ list[list_index] = USE_EXPORTSTR ? savestring (value) !

Bash-4.0 Official Patch 40

-0400 *** *** 2671,2674 --- 2671,2676 word_desc_to_read = (WORD_DESC *)NULL; + eol_ungetc_lookahead = 0; + current_token = '\n'; /* XXX */ last_read_token = '\n'; *** ../bash-4.0/patchlevel.h2009-01-04 14:32:40.000

Bash-4.0 Official Patch 39

ror (_("error importing function definition for `%s'"), name); - - /* ( */ - if (name[char_index - 1] == ')' && name[char_index - 2] == '\0') - name[char_index - 2] = '('; /* ) */ } #if defined (ARRAY_

Re: Explanations of Changes in Bash 4.0 @ http://wiki.bash-hackers.org

> On Thu, Aug 11, 2011 at 03:48:51AM -0800, Roger wrote: >Great website (http://wiki.bash-hackers.org) explaining the changes in bash-4.* >along with all other versions. (The web pages also note it's not a full list >of >changes.) > >In the past, I've scanned Bash's ChangeLog and it didn't provid

Explanations of Changes in Bash 4.0 @ http://wiki.bash-hackers.org

Great website (http://wiki.bash-hackers.org) explaining the changes in bash-4.* along with all other versions. (The web pages also note it's not a full list of changes.) In the past, I've scanned Bash's ChangeLog and it didn't provide any meaningful explanations, just very brief details. (It wou

Re: patch bash32-049 is missing from bash 4.0

> It seems that patch > > http://ftp.gnu.org/gnu/bash/bash-3.2-patches/bash32-049 > > was left from version 4.0. > > Anyone has comment on this? Can this be radded? The changed code is in bash-4.1. Why not just move to that? I put out a patch for 3.2 to accommodate Sun and other vendors, but

patch bash32-049 is missing from bash 4.0

Hi, It seems that patch http://ftp.gnu.org/gnu/bash/bash-3.2-patches/bash32-049 was left from version 4.0. Anyone has comment on this? Can this be radded? Thanks, Petr

Bash-4.0 Official Patch 38

t in unsafe functions being called from signal handlers, which can cause bash to hang or dump core. Patch (apply with `patch -p0'): *** ../bash-4.0-patched/builtins/read.def 2009-09-03 14:40:03.0 -0400 --- builtins/read.def 2010-03-17 17:35:39.0 -0400 ***

Re: [bash-4.0 executes command without newline]

Patch Level: 28 Release Status: release Description: bash executes command without newline This bug was assumed to be fixed with the intregation of bash-4.0, but it is still reproducible. This is not a bug. Shells dating back to v7 have interpreted EOF as a token delimiter equivalent to

Re: [bash-4.0 executes command without newline]

-V890 > Machine Type: sparc-sun-solaris2.11 > > Bash Version: 4.0 > Patch Level: 28 > Release Status: release > > Description: >bash executes command without newline >This bug was assumed to be fixed with the intregation >of bash-4.0, but it is still reproduci

[bash-4.0 executes command without newline]

-xarch=sparcvis -xchip=ultra2 -xO4 -s uname output: SunOS train 5.11 snv_125 sun4u sparc SUNW,Sun-Fire-V890 Machine Type: sparc-sun-solaris2.11 Bash Version: 4.0 Patch Level: 28 Release Status: release Description: bash executes command without newline This bug was assumed to be fixed with

Bash-4.0 Official Patch 35

Bug-Description: Bash-4.0 incorrectly treated single and double quotes as delimiters rather than introducing quoted strings when splitting the line into words for programmable completion functions. Patch: *** ../bash-4.0-patched/pcomplete.c 2009-03-08 21:24:31.0 -0400 --- pcomplete.c

Bash-4.0 Official Patch 34

http://lists.gnu.org/archive/html/bug-bash/2009-09/msg00043.html Bug-Description: When using the globstar option, bash incorrectly interprets wildcarded path components between a **/ and the last / as matching any path, even if the constructed path does not match any files. Patch: *** ../ba

Re: [PATCH] MAILPATH stopped working after update to Bash 4.0

l arriving. However, after I updated to Bash 4.0, I constantly get a "You have new mail." message every minute even though I actually don't have new mail. [...] There was a small change made to the mail file initialization code, to keep from dropping the first "new mail"

Re: [PATCH] MAILPATH stopped working after update to Bash 4.0

w?You have new mail." > >>> MAILCHECK=60 > >>> > >>> Bash 3.2 was correctly telling me about new mail arriving. However, > >>> after I updated to Bash 4.0, I constantly get a "You have new mail." > >>> message every

Re: [PATCH] MAILPATH stopped working after update to Bash 4.0

2 was correctly telling me about new mail arriving. However, >>> after I updated to Bash 4.0, I constantly get a "You have new mail." >>> message every minute even though I actually don't have new mail. Has >>> the mail notification feature changed in Bash

Re: [PATCH] MAILPATH stopped working after update to Bash 4.0

On Tue, May 26, 2009 at 04:11:23PM -0400, Chet Ramey wrote: > Nikos Chantziaras wrote: > > I have: > > > > MAILPATH="/home/me/.maildir/new?You have new mail." > > MAILCHECK=60 > > > > Bash 3.2 was correctly telling me about new mail arriv

Building bash-4.0 on Snow Leopard

Use the attached patch and rebuild configure using `autoconf'. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet

Bash-4.0 Official Patch 33

rchive/html/bug-bash/2009-07/msg0.html Bug-Description: Bash-4.0 has a memory leak in the `read' builtin when the number of fields read is not the same as the number of variables passed as arguments. Patch: *** ../bash-4.0-patched/builtins/read.def 2009-03-08 21:24:45.0

Bash-4.0 Official Patch 32

nu.org/archive/html/bug-bash/2009-08/msg00090.html Bug-Description: Bash-4.0 has a memory leak when processing ${!pre...@}. Patch: *** ../bash-4.0-patched/subst.c 2009-07-22 23:18:55.0 -0400 --- subst.c 2009-08-26 23:08:51.0 -0400 *** *** 6607,6611 }

Bash-4.0 Official Patch 31

ent to index "0" of an existing array variable caused the shell to crash when the variable was unset. Patch: *** ../bash-4.0-patched/arrayfunc.c 2009-03-08 21:24:39.0 -0400 --- arrayfunc.c 2009-08-24 09:29:43.0 -0400 *** *** 99,103 hash = assoc_cr

Bash-4.0 Official Patch 30

ml/bug-bash/2009-07/msg00054.html Bug-Description: A shell function invoked with `bind -x' is supposed to be able to move the cursor by setting READLINE_POINT. The effects of this assignment were sometimes ignored. Patch: *** ../bash-4.0-patched/bashline.c 2009-01-08 09:29:24.

Bash-4.0 Official Patch 29

. Bash-4.0 ignores those names and does not pass them to child processes. Some users and automated processes depend on invalid variables being ignored and passed to child processes. This patch makes bash continue to ignore the invalid names, but pass them to child processes in the export

Re: bash 4.0 segment fault

> >      While i compile with --enable-link-static, gcc stop on finding > > xf_xfree always. Sorry, I can't reproduce this either. Keep in mind that because of how the Linux linker works, you have to configure --without-bash-malloc if you want to use --enable-static-link. Chet -- ``The lyf so

Re: bash 4.0 segment fault

> Hello: >I am now using bash source code 4.0 to compile a binary with > the configure option as following: >--enable-prompt-string-decoding --enable-progcomp > --enable-help-builtin --enable-history --with-bash-malloc=no > >every thing goes smoothy but when I type tab key

Re: bash 4.0 segment fault

sorry, It is sh_xfree but not xf_xfree. On Tue, Sep 8, 2009 at 1:03 PM, Lookey Lam wrote: > Hello: >       I am now using bash source code 4.0 to compile a binary with > the configure option as following: >       --enable-prompt-string-decoding --enable-progcomp > --enable-help-builtin --enable-hi

bash 4.0 segment fault

Hello: I am now using bash source code 4.0 to compile a binary with the configure option as following: --enable-prompt-string-decoding --enable-progcomp --enable-help-builtin --enable-history --with-bash-malloc=no every thing goes smoothy but when I type tab key after i have t

Bash-4.0 Official Patch 28

gi-bin/bugreport.cgi?bug=519165 http://lists.gnu.org/archive/html/bug-bash/2009-07/msg00011.html Bug-Description: bash-4.0 reverted to the historical shell behavior of raising an error when $@ or $* was expanded after `set -u' had been executed and there were no positional

Bash-4.0 Official Patch 27

rchive/html/bug-bash/2009-05/msg00074.html Bug-Description: There are occasional cursor positioning errors when using readline's horizontal scroll mode. Patch: *** ../bash-4.0-patched/lib/readline/display.c 2009-05-22 12:32:25.0 -0400 --- lib/readline/display.c 2009-

Bash-4.0 Official Patch 26

http://lists.gnu.org/archive/html/bug-bash/2009-05/msg00059.html Bug-Description: A forgotten line in externs.h caused compilation errors to occur on some systems (e.g., Cygwin). Patch: *** ../bash-4.0-patched/externs.h 2009-01-18 18:29:29.0 -0500 --- externs.h 2009-06-02 09:05:40.0

Bash-4.0 Official Patch 25

Patch: *** ../bash-4.0-patched/lib/glob/glob.c 2009-05-22 12:32:26.0 -0400 --- lib/glob/glob.c 2009-05-22 12:35:55.0 -0400 *** *** 666,672 } ! /* compat: if GX_ALLDIRS, add the passed directory also, but don't add an ! empty directory name

bash 4.0

I just readed the NEWS for 4.0. Just wanted to say thanks for maintaining and improving bash.

Re: Memory leak within read builtin in both bash 4.0.x and 3.[12].x

wer...@suse.de wrote: > Configuration Information [Automatically generated, do not change]: > Machine: i586 > OS: linux-gnu > Compiler: gcc -I/usr/src/packages/BUILD/bash-4.0 > -L/usr/src/packages/BUILD/bash-4.0/../readline-6.0 > Compilation CFLAGS: -DPROGRAM='bash

Memory leak within read builtin in both bash 4.0.x and 3.[12].x

Configuration Information [Automatically generated, do not change]: Machine: i586 OS: linux-gnu Compiler: gcc -I/usr/src/packages/BUILD/bash-4.0 -L/usr/src/packages/BUILD/bash-4.0/../readline-6.0 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' -DCO

Re: Bash-4.0 Official Patch 23

Eric Blake wrote: > According to Chet Ramey on 6/18/2009 6:55 PM: >> BASH PATCH REPORT >> = > >> Bash-Release: 4.0 >> Patch-ID: bash40-023 > > This appears to also be readline60-003. However, I noticed that although > ftp://ftp.

Re: Bash-4.0 Official Patch 23

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Chet Ramey on 6/18/2009 6:55 PM: >BASH PATCH REPORT >= > > Bash-Release: 4.0 > Patch-ID: bash40-023 This appears to also be readline60-003. However, I noticed that

Re: bash 4.0 on Interix (struct timezone/allsource and broken_dirent_d_no/missing includes)

Jay wrote: > > Is this correct? Pretty much, yes. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/

bash 4.0 on Interix (struct timezone/allsource and broken_dirent_d_no/missing includes)

/src/bash-4.0/execute_cmd.c: In function `time_command': /src/bash-4.0/execute_cmd.c:1145: error: storage size of `dtz' isn't known make: *** [execute_cmd.o] Error 1 /usr/include/sys/time.h: #if defined(_ALL_SOURCE) /* * historical structure for use in 2nd paramter

Bash-4.0 Official Patch 24

h/2009-04/msg00021.html Bug-Description: When using the ** globbing operator, bash will incorrectly add an extra directory name when the preceding directory name ends with `*' or an empty string when there is no preceding directory name. Patch: *** ../bash-4.0-patched/lib/glob/glob.c 2009-

Bash-4.0 Official Patch 23

prompt length exactly matches the screen width, and the prompt ends with invisible characters, readline positions the cursor incorrectly. Patch: *** ../bash-4.0-patched/lib/readline/display.c 2009-01-04 14:32:32.0 -0500 --- lib/readline/display.c 2009-04-25 21:42:18.0 -0400

Bash-4.0 Official Patch 22

g00118.html Bug-Description: When parsing case statements in command substitutions, the shell did not note that a newline is a shell metacharacter and can legally be followed by a reserved word (e.g., `esac'). Patch: *** ../bash-4.0-patched/parse.y 2009-03-08 21:24:47.0 -0400 --- parse

Bash-4.0 Official Patch 21

h/2009-03/msg00149.html Bug-Description: When not in a locale supporting multibyte characters, readline will occasionally not erase characters between the cursor position and the end of the line when killing text backwards. Patch: *** ../bash-4.0-patched/lib/readline/display.c 2009-01-04

Bash-4.0 Official Patch 20

g00104.html Bug-Description: If a SIGWINCH arrives while bash is performing redisplay, multi-line prompts are displayed incorrectly due to the display code being called recursively. Patch: *** ../bash-4.0-patched/lib/readline/readline.h 2009-01-04 14:32:33.0 -0500 --- lib/readline/read

Bash-4.0 Official Patch 19

009-02/msg00200.html Bug-Description: Using an external command as part of the DEBUG trap when job control is enabled causes pipelines to misbehave. The problem has to do with process groups assigned to the pipeline and terminal. Patch: *** ../bash-4.0-patched/jobs.c 2009-01-29 17:09:49.000

Bash-4.0 Official Patch 18

g00184.html Bug-Description: A missing include file results in an empty function definition and a no-op when checking whether or not the window size has changed. Patch: *** ../bash-4.0-patched/lib/sh/winsize.c2008-08-12 13:53:51.0 -0400 --- lib/sh/winsize.c2009-04-06

RE: error building bash-4.0 on Interix/SFU/SUA (MP_RMDOT undeclared, just missing some #includes)

I don't have it handy now but I think bash also had a struct timezone undefined, needed CFLAGS=-D_ALL_SOURCE to get it. - Jay From: jay.kr...@cornell.edu To: bug-bash@gnu.org Subject: error building bash-4.0 on Interix/SFU/SUA (MP_RMDOT undeclared, just missing some #includes)

error building bash-4.0 on Interix/SFU/SUA (MP_RMDOT undeclared, just missing some #includes)

/src/bash-4.0/lib/sh/getcwd.c: In function `_path_checkino': /src/bash-4.0/lib/sh/getcwd.c:80: error: `MP_RMDOT' undeclared (first use in thi s function) /src/bash-4.0/lib/sh/getcwd.c:80: error: (Each undeclared identifier is reported only once /src/bash-4.0/lib/sh/getcwd.c:80: error

Re: is missing in bash-4.0/externs.h

> grep -n FILE build/bash-4.0/externs.h > 200:extern int fpurge __P((FILE *stream)); > 264:extern int sh_setlinebuf __P((FILE *)); > > bash-4.0/externs.h > > needs > > #include Try the attached patch. Including stdio.h in externs.h is the wrong fix. Chet *** ..

Re: MAILPATH stopped working after update to Bash 4.0

Chet Ramey wrote: Nikos Chantziaras wrote: I have: MAILPATH="/home/me/.maildir/new?You have new mail." MAILCHECK=60 Bash 3.2 was correctly telling me about new mail arriving. However, after I updated to Bash 4.0, I constantly get a "You have new mail." message every

Re: MAILPATH stopped working after update to Bash 4.0

Nikos Chantziaras wrote: > I have: > > MAILPATH="/home/me/.maildir/new?You have new mail." > MAILCHECK=60 > > Bash 3.2 was correctly telling me about new mail arriving. However, > after I updated to Bash 4.0, I constantly get a "You have new mail.&q

MAILPATH stopped working after update to Bash 4.0

I have: MAILPATH="/home/me/.maildir/new?You have new mail." MAILCHECK=60 Bash 3.2 was correctly telling me about new mail arriving. However, after I updated to Bash 4.0, I constantly get a "You have new mail." message every minute even though I actually don't

Re: bash 4.0 on arm-linux

cyberGn0m wrote: > A have cross-compiled bash for arm-linux platform. > So, i got problem. > After bash started my context looks broken: > > at start it says: > shell-init: error retrieving current directory: getcwd: cannot access parent > directories: Success It means that getcwd() fails (return

bash 4.0 on arm-linux

A have cross-compiled bash for arm-linux platform. So, i got problem. After bash started my context looks broken: at start it says: shell-init: error retrieving current directory: getcwd: cannot access parent directories: Success cd .. says: chdir: error retrieving current directory: getcwd: can

Re: is missing in bash-4.0/externs.h

On Fri, 2009-05-22 at 10:42 -0700, Sergei Steshenko wrote: > > > --- On Fri, 5/22/09, Chet Ramey wrote: > > > From: Chet Ramey > > Subject: Re: is missing in bash-4.0/externs.h > > To: "Sergei Steshenko" > > Cc: bug-bash@gnu.org, chet.ra...@ca

Re: is missing in bash-4.0/externs.h

--- On Fri, 5/22/09, Chet Ramey wrote: > From: Chet Ramey > Subject: Re: is missing in bash-4.0/externs.h > To: "Sergei Steshenko" > Cc: bug-bash@gnu.org, chet.ra...@case.edu > Date: Friday, May 22, 2009, 9:14 AM > Sergei Steshenko wrote: > > Hello, >

Re: is missing in bash-4.0/externs.h

Sergei Steshenko wrote: > Hello, > > because of the following lines: > > grep -n FILE build/bash-4.0/externs.h > 200:extern int fpurge __P((FILE *stream)); > 264:extern int sh_setlinebuf __P((FILE *)); > > bash-4.0/externs.h > > needs > > #include &g

is missing in bash-4.0/externs.h

Hello, because of the following lines: grep -n FILE build/bash-4.0/externs.h 200:extern int fpurge __P((FILE *stream)); 264:extern int sh_setlinebuf __P((FILE *)); bash-4.0/externs.h needs #include - this was discovered while building under latest officially released CYGWIN. Under Linux

Re: bash 4.0.x sourcing

Gabor Z. Papp wrote: > Hello, > > $ bash --version > GNU bash, version 4.0.17(1)-release (i686-pc-linux-gnu) > Copyright (C) 2009 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > > > This is free software; you are free to change and

bash 4.0.x sourcing

Hello, $ bash --version GNU bash, version 4.0.17(1)-release (i686-pc-linux-gnu) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software; you are free to change and redistribute it. There is NO WARRANTY,

Re: Bash-4.0 - problem with translation!

> There is no way this string can be reasonably be translated into Finnish > because of the structure of the phrase. One way of dealing with this issue > would be to change the string, for example, to "%s can be invoked using > %s" - but I'm not certain what is the context of this phrase (my bes

Bash-4.0 - problem with translation!

Hi! Greetings from Finland! I'm responsible for the Finnish translation of Bash-4.0. Now I have a problem with one phrase: #: builtins/bind.def:307 #, c-format msgid "%s can be invoked via " msgstr "" There is no way this string can be reasonably be translated in

Re: Bash-4.0 crashes with tab expansion of dirnames in $CDPATH

Pekka Niemi wrote: > 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' > -DLOCALEDI

Bash-4.0 crashes with tab expansion of dirnames in $CDPATH

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' -

Bash-4.0 Official Patch 16

sts.gnu.org/archive/html/bug-bash/2009-03/msg00160.html Bug-Description: There are several problems with the handling of $LINENO in an ERR trap. Patch: *** ../bash-4.0-patched/trap.c 2009-01-16 17:07:53.0 -0500 --- trap.c 2009-03-20 21:37:00.0 -0400 ***

Bash-4.0 Official Patch 17

http://lists.gnu.org/archive/html/bug-bash/2009-03/msg00174.html Bug-Description: Adding a null line to a here-document (e.g., by hitting EOF) causes the shell to dump core attempting to dereference the NULL pointer. Patch: *** ../bash-4.0-patched/parse.y 2009-03-08 21:24:47.0 -0400 --- parse.y

Bash-4.0 Official Patch 13

-Description: Though references to $@ when there are no positional parameters will now cause the shell to exit if the `errexit' option has been enabled, constructs such as ${@:-foo} should not cause an exit. Patch: *** ../bash-4.0-patched/subst.c 2009-03-08 21:24:39.0 -0400 --- subst.c 20

Bash-4.0 Official Patch 14

e/html/bug-bash/2009-03/msg00166.html Bug-Description: When the fc builtin is run in a command substitution from a shell with history enabled, it does not correctly calculate the command on which to operate. Patch: *** ../bash-4.0-patched/builtins/fc.def 2009-01-04 14:32:22.0 -0500 --- bu

Bash-4.0 Official Patch 15

http://lists.gnu.org/archive/html/bug-bash/2009-03/msg00174.html Bug-Description: Deferring handling of signals which should cause the shell to terminate until it is "safe" to run the handler functions does not work for some terminating signals. Patch: *** ../bash-4.0-patched/sig.c

Bash-4.0 Official Patch 12

3/msg00129.html Bug-Description: A case statement using the ;& pattern terminator followed immediately by "esac" caused a core dump due to a null pointer dereference. Patch: *** ../bash-4.0-patched/execute_cmd.c 2009-02-13 16:41:41.0 -0500 --- execute_cmd.c 2009-03-14

Bash-4.0 Official Patch 11

nu.org/archive/html/bug-bash/2009-03/msg00092.html Bug-Description: When using the new |& operator following a simple command with a redirection, the redirection of stderr through the pipe was not performed under certain circumstances. Patch: *** ../bash-4.0-patched/parse.y 2009-03-08 21:24:47

Re: bash-4.0 filename completion

Chet Ramey wrote: > This might be the result of changes to the bash readline support function > that dequotes filenames. That function was changed as the result of bug > reports against bash-3.2 to better implement shell quoting. That means: > > 1. Backslashes should not be stripped within sing

Re: bash-4.0 filename completion

Krzysiek Pawlik wrote: > Chet Ramey wrote: >> I can't reproduce this. I get a\ (escaped space), and then listing of >> possible completions with subsequent TABs. This is the correct behavior. >> Could it have something to do with any completion functions you have >> defined? > > Yes, it does. Wh

Re: bash-4.0 filename completion

Chet Ramey wrote: > I can't reproduce this. I get a\ (escaped space), and then listing of > possible completions with subsequent TABs. This is the correct behavior. > Could it have something to do with any completion functions you have > defined? Yes, it does. When I tested without any completio

Re: bash-4.0 filename completion

Krzysiek Pawlik wrote: > Hello, > > With bash-4.0-10 I get following behavior: > > $ touch 'a file with spaces' > $ touch 'a File with spaces' > $ touch 'a File With spaces' > $ cat a > > After pressing TAB completion seems to stop w

bash-4.0 filename completion

Hello, With bash-4.0-10 I get following behavior: $ touch 'a file with spaces' $ touch 'a File with spaces' $ touch 'a File With spaces' $ cat a After pressing TAB completion seems to stop working, pressing Ctrl-i (another bind for `complete') also doesn

Bash-4.0 Official Patch 10

e/html/bug-bash/2009-03/msg00023.html Bug-Description: Bash has problems parsing comments in case statements when they appear in $(...) subshells. Patch: *** ../bash-4.0/parse.y 2009-03-07 15:18:35.0 -0500 --- parse.y 2009-03-07 14:16:32.0 -0500 *** *** 341

Bash-4.0 Official Patch 9

://lists.gnu.org/archive/html/bug-bash/2009-02/msg00255.html Bug-Description: When the read builtin returned due to a timeout supplied with the -t option, it did not restore any modified terminal attribtues. Patch: *** ../bash-4.0/builtins/read.def 2009-01-15 23:11:21.0 -0500 --- b

Bash-4.0 Official Patch 8

e/html/bug-bash/2009-02/msg00230.html Bug-Description: Patch: *** ../bash-4.0/parse.y 2009-01-08 08:29:12.0 -0500 --- parse.y 2009-02-26 17:22:15.0 -0500 *** *** 3443,3448 else shell_ungetc (peekc); ! tflags |= LEX_HER

Bash-4.0 Official Patch 7

009-02/msg00188.html Bug-Description: Bash had a number of problems parsing associative array subscripts containing special characters. The subscripts are supposed to be read as if they are enclosed between double quotes. Patch: *** ../bash-4.0/parse.y 2009-01-08 08:29:12.0 -0500 --- p

Bash-4.0 Official Patch 6

Bug-Description: Bash did not parse pipelines using the |& construct correctly if the pipeline elements were not simple commands. Patch: *** ../bash-4.0/parse.y 2009-01-08 08:29:12.0 -0500 --- parse.y 2009-02-25 17:25:56.0 -0500 *** *** 4478,4481 --- 4478,

Bash-4.0 Official Patch 5

-Description: The `declare' builtin dumped core when attempting to assign associative array indices containing some special characters, even when they were quoted before being expanded. Patch: *** ../bash-4.0/builtins/declare.def2009-01-04 14:32:22.0 -0500 --- builtins/declar

Bash-4.0 Official Patch 4

e/html/bug-bash/2009-02/msg00176.html Bug-Description: In some cases, enabling the `checkjobs' shell option will cause the shell to core dump when executing the `exit' builtin. Patch: *** ../bash-4.0/builtins/exit.def 2009-01-04 14:32:22.0 -0500 --- builtins/exit.def

Bash-4.0 Official Patch 2

nu.org/archive/html/bug-bash/2009-02/msg00142.html Bug-Description: A line inadvertenly omitted from a submitted patch results in core dumps when attempting filename completion while using the bash-completion package. Patch: *** ../bash-4.0/pcomplete.c 2009-02-01 17:12:31.0

Bash-4.0 Official Patch 3

h/2009-02/msg00177.html Bug-Description: Under certain circumstances, constructs containing command substitutions prevent PS1 from being re-evaluated and updated before being displayed. Patch: *** ../bash-4.0/parse.y 2009-01-08 08:29:12.0 -0500 --- parse.y 2009-02-25 15:58:25.000

Bash-4.0 Official Patch 1

ommand substitution is read. Patch: *** ../bash-4.0/parse.y 2009-01-08 08:29:12.0 -0500 --- parse.y 2009-03-06 20:32:35.0 -0500 *** *** 2928,2931 --- 2932,2936 #define LEX_HEREDELIM 0x100 /* reading here-doc delimiter */ #define LEX_STRIPDOC

Re: bash-4.0 regression with comments in subshelled case

On Tuesday 03 March 2009 17:14:16 Chet Ramey wrote: > Mike Frysinger wrote: > > On Tuesday 03 March 2009 15:28:28 Chet Ramey wrote: > >> Mike Frysinger wrote: > >>> code that uses case statements in a subshell and then uses comments > >>> causes bash to trigger a parsing error: > >>> $ cat test.sh

Re: bash-4.0 regression with comments in subshelled case

he attached patch. And note that you don't have to use extra left parens around the pattern lists. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, ITS, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~chet/ *** ../bash-4.0/parse.y 2009-01-08 08:

Re: bash-4.0 regression with comments in subshelled case

On Tuesday 03 March 2009 15:28:28 Chet Ramey wrote: > Mike Frysinger wrote: > > code that uses case statements in a subshell and then uses comments > > causes bash to trigger a parsing error: > > $ cat test.sh > > echo $(case a in (a) echo ok ;; # comment > > ) > > $ sh ./test.sh > > ./test.sh: lin

Re: bash-4.0 regression with comments in subshelled case

Mike Frysinger wrote: > code that uses case statements in a subshell and then uses comments causes > bash to trigger a parsing error: > $ cat test.sh > echo $(case a in (a) echo ok ;; # comment > ) > $ sh ./test.sh > ./test.sh: line 1: unexpected EOF while looking for matching `)' > ./test.sh: lin

bash-4.0 regression with comments in subshelled case

code that uses case statements in a subshell and then uses comments causes bash to trigger a parsing error: $ cat test.sh echo $(case a in (a) echo ok ;; # comment ) $ sh ./test.sh ./test.sh: line 1: unexpected EOF while looking for matching `)' ./test.sh: line 3: syntax error: unexpected end of f

Re: bash 4.0 build error (Mac OS X)

Marius Schamschula wrote: > Hi, > > I just tried building bash 4.0 under Mac OS X. Under 10.3.9, 10.4.11 and > 10.5.6 I get the following error: > > ./lib/sh/libsh.a(getenv.o) definition of _setenv in section (__TEXT,__text) > /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../..

bash 4.0 build error (Mac OS X)

Hi, I just tried building bash 4.0 under Mac OS X. Under 10.3.9, 10.4.11 and 10.5.6 I get the following error: ./lib/sh/libsh.a(getenv.o) definition of _setenv in section (__TEXT,__text) /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libc.dylib(setenv.So) definition of _setenv /usr

Re: bash-4.0 regression with here documents and multiline subshells

cit and to have bash reject it, or to > > fix up this issue so it works again ... > > > > at any rate, this style usage, while seemingly not allowed by the docs, > > works fine with older/current bash: > > echo $(cat <<< "foo") > > > > how

Re: bash-4.0 regression with here documents and multiline subshells

gt; so > it works again ... > > at any rate, this style usage, while seemingly not allowed by the docs, works > fine with older/current bash: > echo $(cat <<< "foo") > > however, when we go multiline, bash-4.0 gets into a parsing loop: > $ cat test.sh > #!/

Re: Associative array indexes not working as expected in Bash 4.0

27;x86_64-unknown-linux-gnu' > -DCONF_VENDOR='unknown' > -DLOCALEDIR='/home/arvid/local/shells/bash/4.0/share/locale' -DPACKAGE='bash' > -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib > -DSYS_BASHRC=/etc/bash/bashrc -DSYS_BASH_LOGOUT=/etc/bash/bas

bash-4.0 regression with here documents and multiline subshells

ge, while seemingly not allowed by the docs, works fine with older/current bash: echo $(cat <<< "foo") however, when we go multiline, bash-4.0 gets into a parsing loop: $ cat test.sh #!/bin/bash echo $( cat <<< "foo" ) $ ./test.sh ./test.sh: li

Re: Problem with function cd in bash 4.0

on Solaris as well. Richard -- View this message in context: http://www.nabble.com/Problem-with-function-cd-in-bash-4.0-tp22171999p0451.html Sent from the Gnu - Bash mailing list archive at Nabble.com.

  1   2   >