Re: |& in bash?

2013-01-18 Thread Dan Douglas
On Thursday, January 17, 2013 06:53:26 PM John Caruso wrote: > In article , Chet Ramey wrote: > > On 1/17/13 1:01 PM, John Caruso wrote: > >> One feature of other shells (e.g. zsh and tcsh) I'd really love to have > >> in bash is "|&", which redirects both stdout and stderr--basically just > >> a

Re: interrupted system call when using named pipes on FreeBSD

2013-01-18 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/18/13 1:45 PM, Mike Frysinger wrote: > On Friday 18 January 2013 07:55:00 Chet Ramey wrote: >> On 1/18/13 1:30 AM, Mike Frysinger wrote: >>> this is somewhat a continuation of this thread: >>> http://lists.gnu.org/archive/html/bug-bash/2008-10/msg

Re: interrupted system call when using named pipes on FreeBSD

2013-01-18 Thread Mike Frysinger
On Friday 18 January 2013 07:55:00 Chet Ramey wrote: > On 1/18/13 1:30 AM, Mike Frysinger wrote: > > this is somewhat a continuation of this thread: > > http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00091.html > > > > i've gotten more or less the same report in Gentoo: > > http://bugs.gent

Re: [PATCH] bash: speed up `read -N`

2013-01-18 Thread Mike Frysinger
On Friday 18 January 2013 07:49:22 Chet Ramey wrote: > On 1/18/13 1:31 AM, Mike Frysinger wrote: > > On Monday 19 November 2012 19:46:17 Mike Frysinger wrote: > >> Rather than using 1 byte reads, use the existing cache read logic. > >> This could be sped up more, but this change is not as invasive

Re: Questions to bash "read" builtin functionality (and supposed problem with while).

2013-01-18 Thread Linus Swälas
On Fri, Jan 18, 2013 at 1:48 PM, Pierre Gaston wrote: > On Fri, Jan 18, 2013 at 2:44 PM, Linus Swälas wrote: >> On Fri, Jan 18, 2013 at 12:56 PM, Pierre Gaston >> wrote: >>> On Fri, Jan 18, 2013 at 1:38 PM, Linus Swälas >>> wrote: On Fri, Jan 18, 2013 at 6:57 AM, Pierre Gaston wro

Re: interrupted system call when using named pipes on FreeBSD

2013-01-18 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/18/13 1:30 AM, Mike Frysinger wrote: > this is somewhat a continuation of this thread: > http://lists.gnu.org/archive/html/bug-bash/2008-10/msg00091.html > > i've gotten more or less the same report in Gentoo: > http://bugs.gentoo.org/447810 > >

Re: [PATCH] bash: speed up `read -N`

2013-01-18 Thread Chet Ramey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/18/13 1:31 AM, Mike Frysinger wrote: > On Monday 19 November 2012 19:46:17 Mike Frysinger wrote: >> Rather than using 1 byte reads, use the existing cache read logic. >> This could be sped up more, but this change is not as invasive and >> should

Re: Questions to bash "read" builtin functionality (and supposed problem with while).

2013-01-18 Thread Pierre Gaston
On Fri, Jan 18, 2013 at 1:38 PM, Linus Swälas wrote: > On Fri, Jan 18, 2013 at 6:57 AM, Pierre Gaston > wrote: >> >> On Thu, Jan 17, 2013 at 4:24 PM, Linus Swälas >> wrote: >>> >>> I have a similar problem to report as Fiedler Roman regarding read and >>> also >>> another problem regarding whil

Re: Questions to bash "read" builtin functionality (and supposed problem with while).

2013-01-18 Thread Linus Swälas
On Fri, Jan 18, 2013 at 6:57 AM, Pierre Gaston wrote: > > On Thu, Jan 17, 2013 at 4:24 PM, Linus Swälas > wrote: >> >> I have a similar problem to report as Fiedler Roman regarding read and >> also >> another problem regarding while. Maybe the while case is intended behavior >> though. =) >> # w