Re: Some globstar patterns produce duplicate entries and a null filename

2012-12-11 Thread Roman Rakus
On 12/10/2012 11:29 PM, Chet Ramey wrote: On 12/5/12 3:17 AM, Roman Rakus wrote: Works well when used up to 2 levels of ** - ** and **/** is fixed. However still produce duplicates, when used more levels - **/**/**. Also produce duplicates for **/a/** form. The next version will treat any seq

Re: Some globstar patterns produce duplicate entries and a null filename

2012-12-11 Thread Chet Ramey
On 12/11/12 5:08 AM, Roman Rakus wrote: > Interesting. So it is up to script writer to delete duplicates. Will you be > interested in patch which will clear duplicates? Let's say it will be some > function run after expansion. And it will be optionally turned on. I guess > it will not have any hig

Re: tab completion with variable expansion broken

2012-12-11 Thread njhwang
Thanks, this is exactly what I needed to fix the issue on my end as well. I'm curious if anyone who patched bash in this manner started seeing a weird issue with long commands in the terminal? After building bash-4.2.29, long commands would no longer break into multiple lines in gnome-terminal, a

How is being invoked via login different?

2012-12-11 Thread Michael Gale
Hello, I gain more knowledge about process controls, jobs and shells I figured it would be interesting to throw together my own shell. Just a simple, throw away test to help me gain knowledge. I was basing a lot of the flow on how bash works however I have hit a problem. My code only work

Re: tab completion with variable expansion broken

2012-12-11 Thread Roman Rakus
On 12/11/2012 06:03 PM, njhwang wrote: Thanks, this is exactly what I needed to fix the issue on my end as well. I'm curious if anyone who patched bash in this manner started seeing a weird issue with long commands in the terminal? After building bash-4.2.29, long commands would no longer break

Several issues with coprocesses regarding exit status

2012-12-11 Thread DJ Mills
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-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale'

Re: Several issues with coprocesses regarding exit status

2012-12-11 Thread Greg Wooledge
On Tue, Dec 11, 2012 at 02:31:28PM -0500, DJ Mills wrote: > First of all, the man page and help output state: > `The return status of a coprocess is the exit status of command.' > No matter what, coproc seems to always return true. > > To reproduce: > coproc false || echo error1 >&2;

Re: Several issues with coprocesses regarding exit status

2012-12-11 Thread DJ Mills
On Tue, Dec 11, 2012 at 2:49 PM, Greg Wooledge wrote: > Since coproc creates a background job, it doesn't really makes sense that > the "coproc" command itself would know the exit status of the background > job. It would have to wait for the background job to terminate first, > which would defea

Re: tab completion with variable expansion broken

2012-12-11 Thread njhwang
I actually did this with a stock Ubuntu .bashrc/PS1 setting, and also tried it with no .bashrc at all and also tried completely clearing PS1, none of which had any effect on this issue. Any other ideas? Thanks -- View this message in context: http://gnu-bash.2382.n7.nabble.com/tab-completion-wi

Re: tab completion with variable expansion broken

2012-12-11 Thread Chet Ramey
On 12/11/12 6:38 PM, njhwang wrote: > I actually did this with a stock Ubuntu .bashrc/PS1 setting, and also tried > it with no .bashrc at all and also tried completely clearing PS1, none of > which had any effect on this issue. Any other ideas? Thanks You don't have the ncurses library installed.