# Tag Info

10

You are inventing your own grouping types. If you open the Options Inspector and go to Cell Options -> General Properties -> CellGroupingRules the drop-down shows several options available: "NormalGrouping", "TitleGrouping", "SectionGrouping", "InputGrouping", "OutputGrouping", "GraphicsGrouping", "GroupTogetherGrouping", and "GroupTogetherNestedGrouping". ...

8

In the course of researching this question, I discovered an answer. Looking at the Option Inspector -> Cell Options -> General Properties for each of the cells shown above, reveals the option: CellGroupingRules. Unfortunately, there is little in terms of documentation for this option. Upon inspection, CellGroupingRules has the value of {"TitleGrouping", ...

8

"Style" /. DeveloperCellInformation[nb] where nb is the NotebookObject for the notebook you care about. Since you could have multiple cells selected, this will always return a list. It's also possible to have no cells selected, in which case CellInformation will return \$Failed and the above code would throw an error.

6

I think I found it but I'd be more than happy to look at other alternatives if any provided: Shift + Ctrl + O to open Options > Notebook options > Evaluation options > Global preferences from the drop down menu at the top Change InitializationCellEvaluation to True and InitializationCellWarning to False The next time the .nb file is launched, the ...

6

If applying a new stylesheet doesn't change the appearance then it looks like the styling is local to each cell. If you have a look at the underlying expression of some of these input cells by going to the menu and choosing Cell > Show Expression you should see some StyleBoxes, as per this example using your code that you have supplied: So if it is the ...

4

Now, with v9, I can undelete this answer :) You could set a context dependent on a certain counter value. Add to your stylesheet, to the "Input" style, the following option CellContext:>"Section"<>ToString@CurrentValue[{"CounterValue", "Section"}]<>"" and in my few tests you get a context dependent on the last section number. It can ...

3

Here are two cells with weird embedded styles, including colors, background colors, and sizes: Select both cells and press Shift+Ctrl+N to re-parse to StandardForm:

3

The link that @rm -rf provides does most of what you have asked for. For the final part of your question Actually, ideally what I'd like to do, is say: Export all cells except the Input and Code cells. i.e. selective Export by types of cells. Evaluate this code -- which you can modify for your particular circumstances -- in your notebook. tmp = ...

2

One possibility would be to (programmatically) add dynamic options to all cells. E.g., one cell could look like : Cell["1-1", "Input", Evaluatable->Dynamic[eval], CellOpen->Dynamic[open], Background->Dynamic[bcolor]] Then, if you evaluate in a subsequenc cell (or by Button) this: eval = True; open = True; bcolor = LightGray the Cell becomes ...

2

CellContext seems to work on the notebook level, although its a Cell option. Anyway the behavior seems to be hardcoded to Mathematica and I wasn't able to see any indication inside the notebook apart from the option. But you can emulate the behavior using the command Begin. For example at the start of each Subsection you can run the command ...

1

Here is the code that should be added to KeyEventTranslations.tr. To learn more about editing this, and similar, system files look at this question and its related. (* Command, d - deletes the current cell (or selected set of cells) and its (or their) related group(s) if the group has exactly 1 Input cell; otherwise deletes only the cell from ...

Only top voted, non community-wiki answers of a minimum length are eligible