Timeline for Skipping sections of a notebook automatically
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 19, 2018 at 15:35 | answer | added | squallseeker | timeline score: 2 | |
| Apr 13, 2017 at 12:55 | history | edited | CommunityBot |
replaced http://mathematica.stackexchange.com/ with https://mathematica.stackexchange.com/
|
|
| Dec 22, 2016 at 16:12 | comment | added | george2079 | It seems there should be a way to use cell tags, tag cells as "debug" for example, then have a keyboard equivalent to control-a that would "select all cells except with the debug tag" | |
| Dec 22, 2016 at 12:18 | answer | added | Adobe | timeline score: 4 | |
| Dec 1, 2015 at 7:45 | comment | added | Kuba | @Jansen What about putting a prolog cell as a first cell in those conditional sections, if the condition is not met it could drop evaluation from parent group and move to next. Is that ok? | |
| Nov 30, 2015 at 20:15 | comment | added | Jansen |
This is indeed close to an answer, but not quite yet. I want to be able to evaluate everything (ctrl+A and shift enter or have another notebook do this) and skip a subsection depending on some condition. Your answer to the other question doesn't seem to achieve this. If I use NotebookLocate["next"]; SelectionEvaluate[EvaluationNotebook[]]; in the beginning of the section that is to be skipped, and i mark some cell in the next section with next, the effect is something else. Everything is evaluated, and after this is done, the cells marked next are evaluated again
|
|
| Nov 30, 2015 at 7:44 | comment | added | Kuba | Maybe this can be marked as a duplicate, what do you think? How to evaluate an input cell automatically after evaluating the previous one. The question is not the same but the answer is similar. | |
| Nov 29, 2015 at 14:38 | comment | added | Michael E2 |
If you mean you've put the code in different cells, then you can use functions like NotebookFind and SelectionEvaluate. But it seems less trouble to do as Yves suggests.
|
|
| Nov 29, 2015 at 13:46 | comment | added | Yves Klett |
Not an answer, but in the long run you might consider consolidating your code into Functions or Modules or even packages to facilitate repeated evaluation. This should also help eliminate errors caused by wrong evaluation order etc..
|
|
| Nov 29, 2015 at 13:33 | history | asked | Jansen | CC BY-SA 3.0 |