Update a note.

1 files changed, 9 insertions, 1 deletions

diff --git a/notes/250219-reader.md b/notes/250219-reader.md
index 503d402..4454783 100644
--- a/notes/250219-reader.md
+++ b/notes/250219-reader.md
@@ -514,7 +514,15 @@ Just to summarize what I actually ended up implementing in the end:
 
   2. Wrap code snippets in one layer of quoting like `'(...)` which
      will effectively protect nested uses of `#QUOTE` from the data
-     decoder, since decoding is a breadth-first operation.
+     decoder, since decoding is a breadth-first operation.  EDIT: No,
+     this won't work, since the decoder also decodes the contents of
+     quoted data, since otherwise `'(foo #(bar))` and such wouldn't
+     work as expected.  I'll think of a solution later.  Maybe there
+     could be a second implementation of `#QUOTE` for data files, and
+     it would not touch the contents at all; one can always run the
+     decoder again explicitly on some data.  The code handling the
+     config file could explicitly decode these super-quoted code
+     snippets before evaluating them.
 
 See here for full documentation of Zisp expressions as implemented: