On Apr 30, 6:57 am, "Greg Landweber" <[EMAIL PROTECTED]> wrote:
Hi Greg,
> You don't need any fancy droplets or applets. You can just use the
> following AppleScript to activate Sage (take this script and save it
> as an AppleScript application, then put it in the same directory as
> the "sage
You don't need any fancy droplets or applets. You can just use the
following AppleScript to activate Sage (take this script and save it
as an AppleScript application, then put it in the same directory as
the "sage" UNIX executable):
tell application "Finder"
set myFolder to container of (
> > I recently downloaded the Vmware version, since Fedora 8 won't let me
> > render 3D (just 2D, I guess I'm gonna have to try the Sun JDK), and
> > I've been pleased with the quality of the plots, there's a lot of
> > potential there, but I still miss the 'good 'ol mesh'. My experience
>
On Tue, Apr 29, 2008 at 5:56 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> On Apr 30, 2:08 am, JoelS <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
>
> > I found the same problem using SAGE 3.0 on a MacBook running OS X.
> > 4.11. Same behavior in both command line and notebook.
> >
> > Here's the error
On Tue, Apr 29, 2008 at 7:51 PM, louie <[EMAIL PROTECTED]> wrote:
>
>
>
> On Mar 31, 1:27 pm, Jason Grout <[EMAIL PROTECTED]> wrote:
> > William Stein wrote:
> > > On Mon, Mar 31, 2008 at 11:03 AM, Jason Grout
> > > <[EMAIL PROTECTED]> wrote:
> > >> Is there an easy way to getmeshlines in a
On Apr 30, 3:06 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
Hi,
> The README file for SAGE's Mac OS X version mentions that easier
> environment integration would be in order, were a Mac OS X developer
> to help. I don't need it myself – I actually prefer to call SAGE
> manually after o
On Mar 31, 1:27 pm, Jason Grout <[EMAIL PROTECTED]> wrote:
> William Stein wrote:
> > On Mon, Mar 31, 2008 at 11:03 AM, Jason Grout
> > <[EMAIL PROTECTED]> wrote:
> >> Is there an easy way to getmeshlines in a plot3d surface?
>
> > This is not implemented. I wish you would implement it :-)
>
>
The README file for SAGE's Mac OS X version mentions that easier
environment integration would be in order, were a Mac OS X developer
to help. I don't need it myself – I actually prefer to call SAGE
manually after opening a terminal window – but has anyone looked into
XDroplets [1]?
XDroplets is
On Apr 30, 2:08 am, JoelS <[EMAIL PROTECTED]> wrote:
Hi,
> I found the same problem using SAGE 3.0 on a MacBook running OS X.
> 4.11. Same behavior in both command line and notebook.
>
> Here's the error report that resulted from trying to plot from command
> line:
>
> *
>
> sage: plot(sin(x
On Apr 29, 9:53 pm, "Jason Martin" <[EMAIL PROTECTED]>
wrote:
Hi,
> I'm running Sage on a RedHat EL box with SELinux turned on (and
> enforcing).
Getting Sage to work with SELinux is not the problem, it is more
knowing which roles are available and how to convince the OS to set
them. It is l
I found the same problem using SAGE 3.0 on a MacBook running OS X.
4.11. Same behavior in both command line and notebook.
Here's the error report that resulted from trying to plot from command
line:
*
sage: plot(sin(x),0,10)
--
i recently installed sage 2.11 and it ran without incident except that
i was unable to run octave fully. this is one problem i would like
worked out, but not the most immediate.
i really like sage, and so installed 3.0 a few days ago as soon as it
came out. installed the binary 'sage-3.0-osx10.4-
On Fri, Mar 28, 2008 at 9:05 AM, kcrisman <[EMAIL PROTECTED]> wrote:
[...]
> Or I could make an init.sage file and put it in, right? It could be
> useful to put a sample of the sort of commands which live in that kind
> of file on the Wiki FAQ, or even a blank file with suggestions
> commente
I'm running Sage on a RedHat EL box with SELinux turned on (and
enforcing). After a bit of fighting with SELinux, here's what I did
to get it working:
1. As root, I created /usr/local/sage and assigned ownership of that
directory to my user account.
The SELinux context of that directory i
-- Forwarded message --
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tue, Apr 29, 2008 at 8:15 AM
Subject: Re: Must SELinux be disabled to run sage?
To: William Stein <[EMAIL PROTECTED]>
Cc: Richard Vaughn <[EMAIL PROTECTED]>
Hi William:
Thanks for the response.
Always ni
I noticed the following behavior today in Linear Algebra, which came up
when trying to make an orthonormal basis. Does anyone know what is
going on?
sage: a=(QQ^3).subspace([[1,0,1]])
sage: b=a.basis()[0]
sage: b/b.norm()
On Tue, Apr 29, 2008 at 9:07 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Apr 29, 5:57 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > On Tue, Apr 29, 2008 at 8:52 AM, mabshoff
>
>
>
>
> > > b) The preparser, i.e. 3.0->RealNumber(3.0): This is a more general
> > > issue, i.e. peop
On Apr 29, 5:57 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Tue, Apr 29, 2008 at 8:52 AM, mabshoff
> > b) The preparser, i.e. 3.0->RealNumber(3.0): This is a more general
> > issue, i.e. people get bitten by it when using numpy/scipy regularly.
> > I am not sure what can be done he
On Tue, Apr 29, 2008 at 8:52 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Apr 29, 5:40 pm, Robert Bradshaw <[EMAIL PROTECTED]>
> wrote:
>
> > On Apr 28, 2008, at 11:32 PM, mabshoff wrote:
>
>
>
>
> > > The file system underneath Sage is for now a Unix file system which
> > > uses "spac
On Apr 29, 5:40 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> On Apr 28, 2008, at 11:32 PM, mabshoff wrote:
> > The file system underneath Sage is for now a Unix file system which
> > uses "space" as a separator. It is generally a bad idea to use
> > anything non [a-zA-Z0-9] in file names
On Apr 28, 2008, at 11:32 PM, mabshoff wrote:
> On Apr 29, 6:24 am, "William Stein" <[EMAIL PROTECTED]> wrote:
>> On Mon, Apr 28, 2008 at 8:25 PM, schmmd <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
>>> Sage has poor support for filenames that contain a space. For
>>> example, if you type `mkdir a\ e'
21 matches
Mail list logo
