On Sat, Oct 1, 2016 at 5:14 PM, William Stein <[email protected]> wrote:
> On Sat, Oct 1, 2016 at 3:31 PM, Stefan van Zwam <[email protected]>
> wrote:
>> Another issue or two:
>>
>> 1) Resizing the browser window on a moderately complex document will freeze
>> the entire browser window for a number of seconds. This is worse on Chrome
>> than in Safari, but happens with both (I'm on a Mac). You can hear the fan
>> spin up, so there must be quite a bit of stuff going on behind the scenes. I
>> used this sample document to verify:
>>
>> https://cloud.sagemath.com/projects/1959a137-a9da-445b-ad23-dae137b1c67e/files/2015-09-10-141729.sagews
>>
>> The momentary freeze also happens when you click away the little "you're on
>> a free server" warning bar, or (in Chrome) when you close the downloads bar
>> at the bottom of the screen.
>
> This slowdown seems to be in the new code for cell input/output
> folding and nested line numbers, so I'll try to make that faster...
I just spent a few hours dramatically speeding the relevant code up,
using various caching and other optimizations. If you try refreshing
your browser enough to clear the cache, you should see a major
improvement -- orders of magnitude.
William
>
>>
>> 2) When I write
>>
>> ** Lemma A.1 ** _Let $A$ be the following matrix:
>> \[
>> \begin{bmatrix}
>> 1 & 1 & 0\\
>> 1 & 0 & 1\\
>> 0 & 1 & 1
>> \end{bmatrix}.
>> \]
>>
>> and my cursor is on the last line after the \], then hitting <enter> does
>> nothing.
>
> This is now fixed; it was
> https://github.com/sagemathinc/smc/issues/199, which wasn't merged
> into master and live yet, for some reason.
>
>>
>>
>> On Saturday, October 1, 2016 at 12:36:12 PM UTC-5, Harald Schilly wrote:
>>>
>>> On Sat, Oct 1, 2016 at 4:19 AM, Stefan van Zwam <[email protected]>
>>> wrote:
>>> > I hear from my student that everything is back to normal. Thanks for the
>>> > quick fix!
>>>
>>> ok, good to know it works! this is not so easy, since several worlds
>>> collide in a single syntax.
>>>
>>> however, I'm aware that there are constructions similar to yours
>>> reported that do not work. I blame it on the markdown parser itself,
>>> and I assume that you aren't writing anything like that anyways: e.g.
>>>
>>> foo _x `x_y` y_ baz
>>>
>>> and the workaround is to wrap this into <i> ... </i> instead.
>>>
>>> -- h
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-cloud" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-cloud/63df5afe-aaba-4be1-a72a-f224fcd84c0f%40googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
>
> Best Regards,
> William Stein
>
> CEO, SageMath, Inc.
--
Best Regards,
William Stein
CEO, SageMath, Inc.
--
You received this message because you are subscribed to the Google Groups
"sage-cloud" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-cloud/CA%2BjwZMgFSme0TAXWAzdZTK48J4Gyhhx_dfGzBFF06j-WqDadxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
