I've taken a look at trac ticket 11026, and I'll comment there as soon as my account is approved. For now:
I'm on OS X Lion, using the Browser bundled with Sage.app. 1. It does start and stop the server. Starting the server initializes three python2.7 processes. Two of them are ~100MB and one is ~5MB. Stopping the server or exiting Sage.app terminates the two larger of these, while leaving the ~5MB python2.7 process running. This last running process is a problem for deleting/renaming Sage.app. 2. Right-clicking a .txt file and selecting Sage.app to open it results in the text of the file being placed above the first input cell without linebreaks. That is, a text file consisting of """Hello. I'm a sample text file in Sage.app""" ends up being opened with the text "Hello. I'm a sample text file in Sage.app", with the first input cell following the text. I'm not quite sure whether this is the intent or not, and I don't imaging using this functionality, personally. 3. Double-clicking a .sws file saved via Sage.app's File->Save As menu does activate Sage.app. It pulls up an error page: "There was an error uploading the worksheet. It could be an old unsupported format or worse. If you desperately need its contents contact the sage-support group and post a link to your worksheet. Alternatively, an sws file is just a bzip2 tarball; take a look inside!" Instead using the in-browser's File->Save worksheet to file... does not appear to save anything. On Saturday, January 5, 2013 3:25:01 AM UTC-6, Ivan Andrus wrote: > > I know I've fixed this before. It took a while to find because it made it > into the patch at #11026 (which would be a great ticket to have finished). > It's there because the issue came up during testing. So if you have some > time it would be great to get it reviewed. IIRC it only needed to be > tested on (Mountain) Lion. > > http://trac.sagemath.org/sage_trac/ticket/11026 > > There are a few other Mac app tickets that need review. If you have some > energy to review them, I have some time to fix whatever issues you find. I > also have some other patches locally that I need to put on trac. > > http://trac.sagemath.org/sage_trac/ticket/10555 > http://trac.sagemath.org/sage_trac/ticket/10556 > > Thanks, > Ivan > > On Jan 5, 2013, at 7:19 AM, Nicholas Kirchner <kirc...@umn.edu<javascript:>> > wrote: > > I've been having the problem that the Mac app won't stop the sage server > when I ask it to. I know the problem: the Mac app source code references > .sage/sage_notebook.sagenb/twistd.pid, whereas it should reference > sagenb.pid. > > The instructions at "Walking Through the Development Process" do not seem > quite suitable for patching the app, which resides in > SAGE_ROOT/devel/ext-main/sage/ext/mac-app. What's the preferred way to > create a patch for a Trac ticket on the Mac application? > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To post to this group, send email to sage-...@googlegroups.com<javascript:> > . > To unsubscribe from this group, send email to > sage-devel+...@googlegroups.com <javascript:>. > Visit this group at http://groups.google.com/group/sage-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
