1.1 --- a/TODO.md	Mon Sep 12 18:02:44 2022 +0200
     1.2 +++ b/TODO.md	Tue Sep 13 10:28:04 2022 +0200
     1.3 @@ -26,7 +26,7 @@
     1.4  
     1.5  ***** for the few items below WN asks MW for help
     1.6  
     1.7 -* MW: make Outer_Syntax.command \<^command_keyword>\<open>problem\<close> a model for ..\<open>Example\<close>
     1.8 +* MW: make Outer_Syntax.command..‹problem› a model for ..\<open>Example\<close>
     1.9    The model should demonstrate, how an ML syntax error is indicated in place 
    1.10    (in the string after \<^keyword>\<open>Given\<close> etc) and not on the definition as a whole. 
    1.11      - in MathEngBasic/problem "Outer_Syntax.command \<^command_keyword>\<open>problem\<close>" there are writeln
    1.12 @@ -34,7 +34,7 @@
    1.13      - in MathEngBasic/problem there is guesswork ("TODO") how to reorganise "fun prep_input_PIDE"
    1.14        such that errors in "Given" etc are indicated WITHIN the term.
    1.15  
    1.16 -* MW: In Outer_Syntax.command \<^command_keyword>\<open>Example\<close> is there a quick fix
    1.17 +* MW: In Outer_Syntax.command..‹Example› help: is there a quick fix
    1.18    for successfully replacing hacked Problem.parse_cas by parse_references_input?
    1.19      (a) In addition to replacing Problem.parse_cas: How implement the optional parser:
    1.20        - Example "Diff_App/No.123 a" + NONE