Alright, I have no idea why I never picked up on this before. If you already knew this and tried to tell me, I apologize for my obtuseness.
Apparently, the reason Capistrano doesn't pick up your .bashrc and such is because Capistrano allocates a pseudo-tty for each command. I'm not sure why I made it do that. However, if I take that particular code out, the .bashrc gets executed for each command, and (as far as my ad-hoc testing goes) it looks like everything still works... I'm going to play with it a bit more, and if I don't find any compelling reason to do otherwise, I'm going to add an option which allows you to explicitly ask for a pty if you need one. The default will be no pty, and hopefully that will be the end of all the grief about Capistrano not reading your login environment. (If any of you happen to have more info about this than I have, I'd appreciate your comments!) - Jamis --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
