On Nov 5, 2011, at 3:44 PM, Martin Albrecht wrote: >>> case "$SHELL_NAME" in > > It's not that terribly important, by this wouldn't work for my ZShell prompt > because i use more advanced features in my prompt. In particular, my prompt > displays the revision number of the hg repository I'm in and whether it's > clean or not. Hence, additional modules need to be loaded for my PS1 to work > as expected.
I have a similar problem in that I set PROMPT_COMMAND to a function in my .bashrc (which does the same thing). The PROMPT_COMMAND remains set when I run `sage -sh` but the actual command isn't defined anymore, so I get warnings until I unset PROMPT_COMMAND. But again, I don't think it's terribly important. There's almost no way we can make everyone's shell work exactly like they want and for those of us who have done "exotic" things, we're probably able to deal with it. -Ivan -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
