Opened 14 years ago

Closed 13 years ago

Last modified 13 years ago

#413 closed enhancement (duplicate)

saving non-evaluated cells

Reported by: was Owned by: boothby
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: notebook Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


On 8/6/07, Ted Kosan <> wrote:
> I am in the process of developing a standard format that typical
> students can follow when using the Sage notebook.  Part of this
> pattern consists of creating cells which contain only comments, like
> the description of a problem that is being solved.  Since comments are
> not executable code, a person would not normally think to press
> <shift><enter> in these cells.
> Unfortunately, if text is entered into a cell without pressing
> <shift><enter>, this text is lost even after the "Save" or "Save and
> close" buttons are pressed.
> Can the behavior of these buttons be changed so that all text in all
> cells is saved when they are pressed?

Yes, definitely.

Change History (4)

comment:1 Changed 14 years ago by was

I think actually whenever text in any cell has changed and

   (1) the cell looses focus, or
   (2) the user clicks "save",

then the contents of that cell should be sent back to the server.
I hate entering a little comment at the top of an input
cell before a 20-second computation, and having to re-run
the computation just to record the comment. 

comment:2 Changed 14 years ago by mabshoff

  • Milestone set to sage-3

comment:3 Changed 13 years ago by boothby

  • Resolution set to duplicate
  • Status changed from new to closed

duplicated by #1590

comment:4 Changed 13 years ago by mabshoff

  • Milestone changed from sage-feature to sage-duplicate/invalid
Note: See TracTickets for help on using tickets.