On Tue, Oct 27, 2009 at 9:06 AM, ghtdak <[email protected]> wrote:
>
> Someday I guess I'll go and see what I might be doing different than
> whats expected or normal... Shell programming and management is a
> magical world that I don't claim to have conquered and very simple
> changes to the .*rc files can have massive unintended consequences.
>
> In my case, when I get the sage shell, all my aliases are gone,
> colorization is gone, the title bar no longer indicates directory...
> and until I remove the extra line printed above the prompt I'm pretty
> much dead... This is a typical 'cd' and 'pwd' session
>
> /mnt/hdd/sage/4.2/sage-4.2
> sage subshell$ pwd
> /mnt/hdd/sage/4.2/sage-4.2
> /mnt/hdd/sage/4.2/sage-4.2
> sage subshell$ cd tarbox
> /mnt/hdd/sage/4.2/sage-4.2
> sage subshell$ pwd
> /mnt/hdd/sage/4.2/sage-4.2/tarbox
> /mnt/hdd/sage/4.2/sage-4.2
> sage subshell$
>
> even looking at it now is confusing. Perhaps its just me. I'm
> getting glasses in a couplea days which might help :-)
>
> My hack is to change PS1 to something static so at least pwd is
> tolerable...
>
> If this is the intended design and folks are happier, I'm fine with
> that... I'll work out a hack to get my aliases and colorization and
> title back into the environment.
We could add a new option that behave like the old one. E.g.,
sage -shrc
is the old one. Can you think of a good name? It would be easy to
implement this:
(1) just add back the old code to the script
SAGE_ROOT/local/bin/sage-sage
(2) add some documentation in the list of advanced options in sage-sage..
(3) sage: hg_scripts.ci()
(4) sage: hg_scripts.export('tip')
Post the resulting patch file.
William
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
