Franco
--
On Tue, Apr 28, 2009 at 11:22 PM, William Stein wrote:
>
> On Tue, Apr 28, 2009 at 1:45 PM, Franco Saliola wrote:
>> On Mon, Apr 27, 2009 at 9:07 PM, William Stein wrote:
>>>
>>> On Mon, Apr 27, 2009 at 11:45 AM, Jason Grout
>>> wrote:
William Stein wrote:
> On Mon,
On Tue, Apr 28, 2009 at 1:45 PM, Franco Saliola wrote:
> On Mon, Apr 27, 2009 at 9:07 PM, William Stein wrote:
>>
>> On Mon, Apr 27, 2009 at 11:45 AM, Jason Grout
>> wrote:
>>>
>>> William Stein wrote:
On Mon, Apr 27, 2009 at 11:29 AM, kcrisman wrote:
> Just as a postscript, I was rea
On Mon, Apr 27, 2009 at 11:45 AM, Jason Grout
wrote:
>
> William Stein wrote:
>> On Mon, Apr 27, 2009 at 11:29 AM, kcrisman wrote:
>>> Just as a postscript, I was really glad to have the autosave a few
>>> minute ago, where I nearly deleted an entire lecture's worth of notes
>>> and computations
> You could have just pressed reload and you would have had your
> worksheet back entirely. It was still sitting there on the server in
> RAM. Never use the back button with the sage notebook, unless you
> immediately press refresh.
>
> william
ok, that seems reasonable! But of course accid
William Stein wrote:
> On Mon, Apr 27, 2009 at 11:29 AM, kcrisman wrote:
>> Just as a postscript, I was really glad to have the autosave a few
>> minute ago, where I nearly deleted an entire lecture's worth of notes
>> and computations which I hadn't saved, by accidentally brushing
>> against a b
On Mon, Apr 27, 2009 at 11:29 AM, kcrisman wrote:
>
> Just as a postscript, I was really glad to have the autosave a few
> minute ago, where I nearly deleted an entire lecture's worth of notes
> and computations which I hadn't saved, by accidentally brushing
> against a browser shortcut to a "fav
Just as a postscript, I was really glad to have the autosave a few
minute ago, where I nearly deleted an entire lecture's worth of notes
and computations which I hadn't saved, by accidentally brushing
against a browser shortcut to a "favorites" page on the wrong window.
(This could happen with "re
I have made a patch that attempts to limit the number of snapshots
that get saved (per worksheet) to an absolute maximum of 30. There's
a bit of a dilemma about just how to do this, given that at present
some users will have more than 30 snapshots for some worksheets, and
in the future this limit
On Fri, Apr 24, 2009 at 5:51 AM, kcrisman wrote:
>
>> > I like the way the proposed patch wipes the slate fairly clean. But I
>> > sort of hope it is temporary and at some point a rational autosave
>> > strategy of some sort is implemented. There was an attempt to not
>
> The only issue is th
On Fri, Apr 24, 2009 at 5:51 AM, kcrisman wrote:
>
>> > I like the way the proposed patch wipes the slate fairly clean. But I
>> > sort of hope it is temporary and at some point a rational autosave
>> > strategy of some sort is implemented. There was an attempt to not
>
> The only issue is th
On Fri, Apr 24, 2009 at 12:35 AM, Stan Schymanski wrote:
>
> +1 for a 'smart' auto backup system. I don't know whether it was the
> snapshot saving or what did it, but I never bothered saving notebooks
> while working with them and never lost any data after crashes.
When a snapshot is taken the
> > I like the way the proposed patch wipes the slate fairly clean. But I
> > sort of hope it is temporary and at some point a rational autosave
> > strategy of some sort is implemented. There was an attempt to not
The only issue is that there is no guarantee that the autosave, in
some "ratio
+1 for a 'smart' auto backup system. I don't know whether it was the
snapshot saving or what did it, but I never bothered saving notebooks
while working with them and never lost any data after crashes. It is
such a great peace of mind not to have to remember to save your work
regularly and sti
On Apr 22, 5:36 pm, William Stein wrote:
> Does anybody here ever use snapshots?
I have never used a snapshot, that I am aware of. I've lost a cell or
two due to crashes, but I think this was always due to my flaky USB
hard drive setup and not Sage's fault. And it was always just messing
aroun
On Thu, Apr 23, 2009 at 5:14 PM, William Stein wrote:
>
> On Thu, Apr 23, 2009 at 2:13 PM, Timothy Clemans
> wrote:
>>
>> On Thu, Apr 23, 2009 at 4:34 PM, William Stein wrote:
>>>
>>> Hi,
>>>
>>> I've written a patch against 3.4.1:
>>>
>>> http://trac.sagemath.org/sage_trac/ticket/5880
>>>
>>>
On Thu, Apr 23, 2009 at 2:13 PM, Timothy Clemans
wrote:
>
> On Thu, Apr 23, 2009 at 4:34 PM, William Stein wrote:
>>
>> Hi,
>>
>> I've written a patch against 3.4.1:
>>
>> http://trac.sagemath.org/sage_trac/ticket/5880
>>
>> which simply greatly reduces the number of situations that result in
>
On Thu, Apr 23, 2009 at 4:34 PM, William Stein wrote:
>
> Hi,
>
> I've written a patch against 3.4.1:
>
> http://trac.sagemath.org/sage_trac/ticket/5880
>
> which simply greatly reduces the number of situations that result in
> snapshots. Basically, now you get them when you click "save". Ther
Hi,
I've written a patch against 3.4.1:
http://trac.sagemath.org/sage_trac/ticket/5880
which simply greatly reduces the number of situations that result in
snapshots. Basically, now you get them when you click "save". There
is no autosave.
Please try/test.
-- William
On Thu, Apr 23, 2009
I definitely agree with those who would keep snapshot. Having a list
of commands is not the same - for one thing, log does not save the
whole worksheet, only commands (i.e. not TinyMCE stuff); for another,
it logs notebook-wide, so it becomes a bit of a jaunt to find stuff.
That said, I also agr
I have used snapshots when I forgot to save a notebook under a new name
before making big changes and then wanted to revert to the original. It
wasn't very convenient, as the plots are not saved, so I could not
easily recognise the right version. However, it saved my day!
I like the idea of jus
On Wed, Apr 22, 2009 at 5:49 PM, Jason Grout
wrote:
>
> William Stein wrote:
>> On Wed, Apr 22, 2009 at 5:21 PM, kcrisman wrote:
>>>
>>>
> There are a good many patches out there to address small aspect of
> these problems. In #4886 and #4887 Timothy Clemans has some good
> ideas fo
William Stein wrote:
> On Wed, Apr 22, 2009 at 5:21 PM, kcrisman wrote:
>>
>>
There are a good many patches out there to address small aspect of
these problems. In #4886 and #4887 Timothy Clemans has some good
ideas for renaming some variables and making default save periods
On Wed, Apr 22, 2009 at 5:21 PM, kcrisman wrote:
>
>
>
>> > There are a good many patches out there to address small aspect of
>> > these problems. In #4886 and #4887 Timothy Clemans has some good
>> > ideas for renaming some variables and making default save periods
>> > configurable from the "
> > There are a good many patches out there to address small aspect of
> > these problems. In #4886 and #4887 Timothy Clemans has some good
> > ideas for renaming some variables and making default save periods
> > configurable from the "Settings" page of the notebook. However, these
> > patche
On Wed, Apr 22, 2009 at 1:40 PM, Rob Beezer wrote:
>
> Here's my $0.02 worth on worksheet management as part of the notebook
> interface.
>
> For most new users the notebook is the face of Sage initially. And it
> is very impressive. But I worry about users seeing the (very
> frustrating) slowd
Here's my $0.02 worth on worksheet management as part of the notebook
interface.
For most new users the notebook is the face of Sage initially. And it
is very impressive. But I worry about users seeing the (very
frustrating) slowdowns that Jason and I experienced after heavy use
(tens or hundre
I think auto_save_interval could refer to worksheets, while
save_interval might refer to nb.sobj. This is part of the problem
here - there are variables, keywords and page headings (via "Settings"
in the notebook) that are vague or misleading, and even my attempt to
add a bit of documentation to
Followup:
> The original patch athttp://trac.sagemath.org/sage_trac/ticket/5371
> has some comments in it about extending the default save times if you
> wnt to take immediate action. Some of the names of these autosave
> variables are mildly misleading, though this is corrected in some of
> the
Dear Rob,
>
> > 1. You can delete all your old snapshots to reclaim disk space (or
> > relieve quota limits in a shared environment). I used some
> > incantation with find, xargs, and rm (carefully) which cleared them
> > out for every worksheet all at once. Like Jason I had a few gigabytes
>
On Wed, Apr 22, 2009 at 9:15 AM, Rob Beezer wrote:
>
> kcrisman,
>
> You've discovered the tangle of tickets on this I alluded to
> above. ;-)
>
> 1. You can delete all your old snapshots to reclaim disk space (or
> relieve quota limits in a shared environment). I used some
> incantation with
kcrisman,
You've discovered the tangle of tickets on this I alluded to
above. ;-)
1. You can delete all your old snapshots to reclaim disk space (or
relieve quota limits in a shared environment). I used some
incantation with find, xargs, and rm (carefully) which cleared them
out for every wor
31 matches
Mail list logo
