On Tue, May 08, 2012 at 08:14:16PM +0200, Stephan Beal wrote: > On Tue, May 8, 2012 at 7:56 PM, Lluís Batlle i Rossell > <vi...@viric.name>wrote: > > > But most relevant for this case, is that a login shell runs > > ".bash_profile", and > > a non-login shell runs ".bashrc". non-interactive sessions should use > > non-login > > > > Slight correction - that's only for /bin/bash. Not everyone uses bash and > not all platforms default to it (e.g. solaris).
Well, I imagine every shell has that clear distinction. In any case, there is /etc/profile, ~/.profile, additional to ~/.bash_profile. zsh does something similar on ~/.profile csh/tcsh do the same: .tcshrc/.cshrc vs .login > That said, fossil should not do "ssh host", without command, because that's > > meant to produce text for humans that fossil may fail to parse. > > > > It's also used as a way of calling local scripts on remote hosts: > > cat foo.sh | ssh host It can work for most cases... unless your 'profile' script asks you for a password :) But people mostly add output text to .bash_profile, jkkkkkkkkkkkkkk cat foo.sh | ssh host | sort # Trying to use the output may be worse. You should run: cat foo.sh | ssh host sh | sort _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
