1* Allow execution with cpp(1) to support #include as2 done by calendar(1) and the Xresources parser.3* Allow associating more information with references,4 for instance to allow referencing specific pages5* Less syntactic restrictions for optional notes6 * Allow references in notes7 * Allow newlines in note entries. Alternatively, explicitly8 advocated single-lines notes for clarity. Figure out what9 works best by experimenting with this a bit.10 * Allow markdown-like syntax, e.g. headings, et cetera11* Consider allowing specific unicode characters as note start12 characters. For example ↳ or →.13* Considering adding support for an "in-progress" entry state (e.g. |).14* Experiment with using wikidata IDs for topics (e.g. Q179310)1516* Add readit-def tool for finding the line number and file where a17 reading list entry has been defined. This has to be done after CPP18 integration as CPP integration (#include) will make doing so more19 difficult.20 * If combined with CPP integration parsing of CPP markers is necessary21 * Syntax for CPP markers maybe vary across different implementations22 * For GCC documented here: https://gcc.gnu.org/onlinedocs/gcc-7.2.0/cpp/Preprocessor-Output.html#Preprocessor-Output23* Add readit-fields tool for finding fields by value24 * Should allow listing all field names, like `beet fields` to25 ensure consistency regarding entry field names2627* Alternative design: Use markdown for notes, only use readit format for28 fields. This would be similar to Jekyll's approach for combining29 metadata with text by using markdown with inline yaml.