5
$\begingroup$

They seem to be correctly interpreted.

I'm asking because of some minor reasons and a major one: NotebookWrite a Cell with WholeCellGroupOpener option

I don't know any official confirmation so let me just ask if anyone knows where using string names for built in options names may fail.

Let's assume the context is only about Cell options.


As we can see, works well:

CellPrint[
 Cell[TextData["Test"], "Input", "Background" -> LightBlue, 
  "CellFrame" -> True, "FontColor" -> Red]]

Cell expression (Ctrl+Shift+E) shows that "Background" was converted to Background but even if I manually edit the cell back to "Background" it understands it.

$\endgroup$
4
  • $\begingroup$ Thou shalt support other MMA User and thou shalt fight against Spam. +1 $\endgroup$
    – user9660
    Jul 22, 2015 at 13:20
  • $\begingroup$ Maybe if the symbol does not exist in the System` context? $\endgroup$ Jul 22, 2015 at 20:30
  • $\begingroup$ @RolfMertig It works well for both, System and Global, that's why I'd like to use it. $\endgroup$
    – Kuba
    Jul 22, 2015 at 21:21
  • $\begingroup$ I like doing this too. Makes for easier reading. Please post if you find any options that are not supported this way. $\endgroup$
    – B flat
    Dec 18, 2015 at 4:17

1 Answer 1

2
$\begingroup$

I've talked with John Fultz and he confirmed this should work and be a stable remedy for the context problem linked above.

$\endgroup$

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.