Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Copied worksheets do not remember whether the "Typeset" option is active #12537

Closed
sagetrac-olazo mannequin opened this issue Feb 19, 2012 · 7 comments
Closed

Copied worksheets do not remember whether the "Typeset" option is active #12537

sagetrac-olazo mannequin opened this issue Feb 19, 2012 · 7 comments
Assignees
@jasongrout @williamstein @qed777
Labels
c: user interface r: invalid t: bug

Comments

@sagetrac-olazo
Copy link
Mannequin

sagetrac-olazo mannequin commented Feb 19, 2012

If I tick the Typesett option in the notebook, and then go to File-> Copy worksheet, the resulting copied worksheet will not have that option ticked.

Upstream: Reported upstream. Developers acknowledge bug.

CC: @dimpase @fchapoton

Component: notebook

Issue created by migration from https://trac.sagemath.org/ticket/12537
@sagetrac-olazo sagetrac-olazo mannequin added this to the sage-5.11 milestone Feb 19, 2012
@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@kcrisman
Copy link
Member

Reviewer: Karl-Dieter Crisman

@kcrisman
Copy link
Member

comment:5

This was fixed at some point, probably when Jmol was updated to jsmol and we spent a lot of time worrying about two new checkboxes.

@kcrisman kcrisman removed this from the sage-6.4 milestone Dec 11, 2014
@kcrisman
Copy link
Member

comment:7

Hold up, I may have misinterpreted this...

@kcrisman
Copy link
Member

Upstream: Reported upstream. Developers acknowledge bug.

@kcrisman
Copy link
Member

Changed reviewer from Karl-Dieter Crisman to none

@kcrisman
Copy link
Member

comment:8

Indeed, I can confirm this, and have reported it sagemath/sagenb#303

@kcrisman kcrisman added this to the sage-6.5 milestone Dec 11, 2014
@mkoeppe
Copy link
Member

mkoeppe commented Aug 17, 2020

comment:9

outdated, should be closed

@mkoeppe mkoeppe removed this from the sage-6.5 milestone Aug 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jasongrout jasongrout

@williamstein williamstein

@qed777 qed777

Labels
c: user interface r: invalid t: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@jasongrout @williamstein @kcrisman @jdemeyer @fchapoton @mkoeppe