6
$\begingroup$

Bug introduced in 9.0 or earlier and fixed in 10.3


Consider this:

NotebookWrite[EvaluationNotebook[], 
  Cell["Foo", "Text", Copyable -> False, CellTags -> "example"]];
NotebookFind[EvaluationNotebook[], "example", All, CellTags];
NotebookDelete[];

Execute that. You'll hear a beep, and the generated cell does not disappear. The Help menu's "Why the beep?" command helpfully explains that

"The material you tried to copy had the option Copyable->False set, preventing it from being copied to the clipboard."

Wait, what? I was trying to delete, not copy. The cell has Deletable->True by default.

My question is: Why does NotebookDelete fail on a cell for which Copyable->False? It doesn't copy. (I checked. With Copyable->True, the delete succeeds, and my system clipboard contains what it previously had, not the deleted cell.)

Is this perhaps a bug? (I'm using Mathematica 10.2.0.0 on OS X.)

$\endgroup$
  • $\begingroup$ It's the same in v9. Seems weird. Manual delete fails too (Edit -> Clear or the Delete key) I'd ask support about it ... $\endgroup$ – Szabolcs Aug 11 '15 at 20:37
  • $\begingroup$ Okay, I just submitted something. I'll post again if/when I hear a response. Thanks. $\endgroup$ – ibeatty Aug 11 '15 at 20:41
  • $\begingroup$ I have received a short and simple response from Wolfram tech support, informing me that they have "filed a bug report with the development team" and stating that "hopefully it would be improved in future release." So yes, I guess that makes it a bug. $\endgroup$ – ibeatty Aug 12 '15 at 20:06
  • $\begingroup$ Newbie meta-question: Does acknowledgement of a bug count as an "answer" that I should post as such (and accept)? $\endgroup$ – ibeatty Aug 12 '15 at 20:07
  • $\begingroup$ I think it's okay if you post an answer and mention the response you got from support. It will prevent the system from periodically bumping this post to the top as "unanswered". I added the bug-header for the sake of searchability. $\endgroup$ – Szabolcs Aug 12 '15 at 20:21
3
$\begingroup$

To summarize and move from an unanswered stack:

I have received a short and simple response from Wolfram tech support, informing me that they have "filed a bug report with the development team" and stating that "hopefully it would be improved in future release." So yes, I guess that makes it a bug.

– ibeatty Aug 12 at 20:06

And indeed it is fixed. At least on Win and V10.3

$\endgroup$
  • $\begingroup$ Thanks for doing that. Sorry, I lost track of this thread and forgot to self-answer. $\endgroup$ – ibeatty Nov 24 '15 at 18:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.