Re: Subshell lost ANSI colors

2016-10-20 Thread Thomas Wolff
Am 20.10.2016 um 21:06 schrieb Evgeny Grin: Hi! Noticed some time ago: most of subshells lost colors and prints some codes. Sample output: User@PcName ~ $ dash \[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\

Re: subshell redirection (/dev/fd/x)

2009-02-17 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Mark J. Reed on 2/17/2009 12:17 PM: > On Tue, Feb 17, 2009 at 2:11 PM, Tim McDaniel wrote: >> I think that, out of the box, <(...) doesn't work under Cygwin. We had to do >>ln -s /proc/self/fd /dev/fd > > FYI, I have that symlink in

Re: subshell redirection (/dev/fd/x)

2009-02-17 Thread Mark J. Reed
On Tue, Feb 17, 2009 at 2:11 PM, Tim McDaniel wrote: > I think that, out of the box, <(...) doesn't work under Cygwin. We had to do >ln -s /proc/self/fd /dev/fd FYI, I have that symlink in a vanilla Cygwin 1.5 install... -- Mark J. Reed -- Unsubscribe info: http://cygwin.com/ml/#unsub

Re: subshell redirection (/dev/fd/x)

2009-02-17 Thread Tim McDaniel
On Tue, 17 Feb 2009, Brian Ford wrote: $ uname -a CYGWIN_NT-5.1 PC1163-8460A-XP 1.7.0(0.193/5/3) 2009-02-09 22:27 i686 Cygwin Just curious if the following is known behavior? $ echo a | tee >(wc) a tee: /dev/fd/63: Bad file descriptor $ 0 0 0 The bash term is "Process Subs

Re: Subshell

2004-03-12 Thread Gregory Borota
Sorry, it should have been #! (beginners mistake, I guess) Thanks, Greg On Fri, 12 Mar 2004, Christopher Faylor wrote: > On Fri, Mar 12, 2004 at 01:49:27PM -0600, Gregory Borota wrote: > >#/bin/bash > >echo Silly > >( sleep 50 & > > ( sleep 50 ) ) > >wait > > > >each subshell is "sh.exe". > > Why

Re: Subshell

2004-03-12 Thread Christopher Faylor
On Fri, Mar 12, 2004 at 01:49:27PM -0600, Gregory Borota wrote: >#/bin/bash >echo Silly >( sleep 50 & > ( sleep 50 ) ) >wait > >each subshell is "sh.exe". Why would bash arbitrarily choose "sh.exe" as the subshell? >I want to be be "bash.exe". How do I force that without having to >write bash -c