Thanks!
On May 25, 6:27 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 5/25/07, Utpal Sarkar <[EMAIL PROTECTED]> wrote:
>
> > I thought it could work something like this:
>
> Thanks for your detailed feedback.
> [...] and moreover
>
> > there were the possibility to specify a startup scrip
On 5/25/07, Utpal Sarkar <[EMAIL PROTECTED]> wrote:
> I thought it could work something like this:
Thanks for your detailed feedback.
[...] and moreover
> there were the possibility to specify a startup script which would be
> executed just before entering the session (like in magma when called
>
I thought it could work something like this:
As a command line option it could be like an include path or a library
path to gcc, i.e. every option "-I path" (or any other name of the
switch, this is the one for includes in gcc) is added to the existing
default list of paths. This could be useful e
Thank you sensei!
On May 24, 5:21 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> I've attached the hg patch that fixes the notebook problem you've
> been reporting. You can apply it with
>hg_sage.apply('4585.patch')
> followed by "sage -br" (which will take 10 minutes)..
> Or, just wait f
On 5/25/07, doetoe <[EMAIL PROTECTED]> wrote:
>
> Is there a way to set a search path for sage files (for load and
> attach), e.g. by means of an environment variable or by passing a
> command line option when starting sage?
> I looked for it in the documentation, but I couldn't find anything.
Th
Is there a way to set a search path for sage files (for load and
attach), e.g. by means of an environment variable or by passing a
command line option when starting sage?
I looked for it in the documentation, but I couldn't find anything.
--~--~-~--~~~---~--~~
To
