aboutsummaryrefslogtreecommitdiffhomepage
path: root/data/doc/sisu/sisu.org
diff options
context:
space:
mode:
Diffstat (limited to 'data/doc/sisu/sisu.org')
-rw-r--r--data/doc/sisu/sisu.org15
1 files changed, 12 insertions, 3 deletions
diff --git a/data/doc/sisu/sisu.org b/data/doc/sisu/sisu.org
index 265abda9..8800572d 100644
--- a/data/doc/sisu/sisu.org
+++ b/data/doc/sisu/sisu.org
@@ -2247,15 +2247,24 @@ consider,
I have to date deliberately tried to keep it easy to follow documents & not have too much depth ...
The idea of recursive includes is un-attractive (messy for a document)
-.ssm currently can contain .sst or .ssi
+.ssm currently can contain/include .sst or .ssi
.sst files can be processed independently,
-.ssi files are only insertions & cannot
+.ssi files are only insertions & are not processed independently but as part of an ssm
+
+change proposed
+.ssm unchanged
+.sst unchanged
+.ssi as before, but can include .sst or .ssi, so:
+ files are only insertions & are not processed independently but as part of an .ssm or another .ssi
+ i.e. as before with the addition that it like a .ssm can contain/include .sst or .ssi
+
+this is pretty much as requested by wishlist 744408
allowing .ssi to also include other .ssi or .sst could lead to recursive .ssi
-allowing .ssm to also include other .ssm .ssi or .sst could lead to recursive .ssm
stopping after an additional level of includes seems arbitrary, and possibly prone to error if you are dealing with many documents
+***** Discard
a possibility would be to have another file extension to flag the role of the file,
.ssmi (not very attractive) might do it
(providing visual cue signalling its role as both a master file and an insertion/included file that cannot be processed independently)