All... The issue is resolved!
It was that I had some fancy coloring options in my .bashrc in the account on the production server that was being used to deploy. export CLICOLOR=1 # use yellow for directories export LSCOLORS=dxfxcxdxbxegedabagacad Commenting out the above two lines resolved the issue and prevented the ASCII formatting characters from being included in the command. Thanks to all who took the time to respond with suggestions. Chris On Mar 17, 8:34 pm, Rafa García <[email protected]> wrote: > Hi Chris, > > Could you put your shell(/bin/sh) configurations? It's to try to see why > escape terminal codes > > Good night > > 2011/3/18 Chris Benes <[email protected]> > > > > > Lee... > > > Why would it be bundle? Isn't capistrano just passing the command > > string to the remote server and bundle is a parameter of that string? > > > Prior non-bundle commands work fine though. > > > Chris > > > On Mar 17, 5:42 pm, Lee Hambley <[email protected]> wrote: > > > \e[33m > > > > is the terminal escape code for `brown` text… I have no idea where that's > > > coming from - first thought it something in your shell profile > > contaminating > > > the return of your shell commands. It could also just be bundler… in > > which > > > case, check with them on their mailing list! > > > > - Lee > > > -- > > * You received this message because you are subscribed to the Google Groups > > "Capistrano" group. > > * To post to this group, send email to [email protected] > > * To unsubscribe from this group, send email to > > [email protected] For more options, visit this group > > athttp://groups.google.com/group/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
