| commit | 13a46476e4d885bfa7be89a7fb3f45bcc53825e1 | |
| author | malc <clamky@hotmail.com> | |
| Fri, 28 Jan 2022 20:20:52 +0000 (28 23:20 +0300) | ||
| committer | malc <clamky@hotmail.com> | |
| Fri, 28 Jan 2022 20:20:52 +0000 (28 23:20 +0300) | ||
| tree | 51553334b5555c3e9ea6256f21848e1ae6affbf9 | treesnapshot (tar.gz zip) |
| parent | dc906ffdcec7ac5fc9bb3fb4e08dcb00deaf92dd | commitdiff |
Remove bogus(?) assert
01ff5cb4ce0471bd4974e60d8a8eaaf4ce71d994 commented out redisplay and
added assert, without specifying why, will err on the side of "it was
a debugging leftover" (after all the commit in question was a WIP) and
return things to the way they were (i.e. post redisplay instead of
dying)
Currently the assert can be triggered while navigating ML2015-talk.pdf
in presentation mode.
01ff5cb4ce0471bd4974e60d8a8eaaf4ce71d994 commented out redisplay and
added assert, without specifying why, will err on the side of "it was
a debugging leftover" (after all the commit in question was a WIP) and
return things to the way they were (i.e. post redisplay instead of
dying)
Currently the assert can be triggered while navigating ML2015-talk.pdf
in presentation mode.
| main.ml | diffblobblamehistory |