Development snapshot

Hello, is there something like a development snapshot for Bash 4 or is the code "hidden" during development phase and I need to wait for the first release? Thanks in advance, Jan -- This is my life - this is my net! - Jan

Re: Regular experssions are not working in 3.2.39 as in 3.1.17

[EMAIL PROTECTED] wrote: > regular expression are broken in 3.2.39 It's not broken; it's different. See entry E14 in the bash FAQ, and check out the compat31 option in shopt. paul

Regular experssions are not working in 3.2.39 as in 3.1.17

Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba

Re: "tcsetattr: Interrupted system call" after rapid-fire ^C chars

Chet Ramey wrote: > Joe Peterson wrote: > >> Well, without a hacked kernel, you'll probably not hit >> *this* manifestation of the issue, but what I did was: >> >> - run a text processing program (like "cat" or "tr") >> - hit ctrl-S >> - enter lots of text t

Re: Readline : move to previous/next path component

Andre Majorel wrote: > One frequently needed function that readline does not seem to > have is a way to move to the beginning of the next or previous > path component. This is what I've come up with : > > \C-t: "\C-b\C-b\e\C-]/\C-f" > \C-y: "\C-]/\C-f" Readline doesn't have any built-in knowl

Re: "tcsetattr: Interrupted system call" after rapid-fire ^C chars

Joe Peterson wrote: > Well, without a hacked kernel, you'll probably not hit > *this* manifestation of the issue, but what I did was: > > - run a text processing program (like "cat" or "tr") > - hit ctrl-S > - enter lots of text that will then produce lots

Re: 'bash -c' does not execute 'trap ... EXIT' command when last command is an external command

Steffen Kieß wrote: > 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' -DLOCAL

Re: why does bash not execute .bashrc with ssh -t ?

Jon Seymour wrote: > Bash attempts to determine when it is being run by the remote shell > daemon, usually rshd. If bash determines it is being run by rshd, it > reads and executes > commands from ~/.bashrc, if that file exists and is readable. It > will not do this if invoked as sh

why does bash not execute .bashrc with ssh -t ?

I am trying to work out why .bashrc is not executing when I invoke ssh with the -t option and _does_ execute when I invoke ssh without the -t option. ssh -qt remote-host which rsync # indicates ~/.bashrc has not executed on remote host ssh -q remote-host which rsync # indicates ~/.bashrc has

Readline : move to previous/next path component

One frequently needed function that readline does not seem to have is a way to move to the beginning of the next or previous path component. This is what I've come up with : \C-t: "\C-b\C-b\e\C-]/\C-f" \C-y: "\C-]/\C-f" Three problems with this kludge : 1. The definition uses keys, not funct

"tcsetattr: Interrupted system call" after rapid-fire ^C chars

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/local