On Fri, Dec 23, 2016 at 12:11 AM, David Joyner <wdjoy...@gmail.com> wrote: > Erik Bray: > > Many thanks for this. Great job. > > I tested latest version on a windows 7 machine in a computer lab at > work. The sage terminal worked fine. The sage notebook didn't work > well in IE (the default browser). In chrome, it worked but was a > little slow. For example, "2+3" took a second or so. Do you know why? > I noticed a message "timeout waiting for kernel_info" in the console.
Great, thanks for testing. That's good the CLI worked fine. Mysterious about the notebook though--you're the first I think to report anything like that. What do you mean by it "didn't work well in IE"? Sometimes the first command takes a little longer than most as there's some startup overhead, but a second is on the long side. After that it should not be so slow. At the moment the only reason I can think of is something odd in the Windows firewall settings. > On Thu, Dec 15, 2016 at 5:20 AM, Erik Bray <erik.m.b...@gmail.com> wrote: >> On Wed, Dec 14, 2016 at 9:10 PM, Peter Luschny <peter.lusc...@gmail.com> >> wrote: >>>> I replaced the existing binary with a new one at >>> >>> BRAVO! >>> All works fine. >> >> Great! >> >>> (only plot() gives no output) >> >> That's strange... I thought I fixed that, and it works for me. >> >> All it's doing to determine the image viewer is passing the file to >> cygstart (cygstart is a program that comes with Cygwin that just uses >> the Windows API to find the default program file the given file >> type--in this case PNG I assume?) >> >> Maybe if you start up the "SageMath Shell" and manually run `cygstart >> <path-to-some-png>` we can see what happens. >> >> Also, it was pointed out to me by someone else that the "SageMath >> Console" shortcut link in the latest build is broken (it just has a >> typo). >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-devel+unsubscr...@googlegroups.com. >> To post to this group, send email to sage-devel@googlegroups.com. >> Visit this group at https://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
