document: Inter snippet source text into the xapian index.

We store snippet source text in a slot of the <document> class thus
interring into the xapian index. This allows us to render search
snippets using only the xapian index without referring back to the git
repository.

* tissue/document.scm (<document>)[snippet-source-text]: New slot.
* tissue/document.scm (document-snippet-source-text): Delete method.
(document-html-snippet): Remove blank lines from snippet source text
before generating a snippet.
* tissue/commit.scm (document-snippet-source-text): Delete method.
(repository-commits): Initialize snippet-source-text.
* tissue/skribilo.scm (fragment-text): New function.
(document-fragment): Initialize snippet-source-text.
(document-text): Use fragment-text.
(document-snippet-source-text): Delete method.
* tissue/file-document.scm (file-text): New function.
(document-text): Use file-text.
(read-gemtext-document): Initialize snippet-source-text.
* tissue/issue.scm (read-gemtext-issue): Initialize
snippet-source-text.
* issues/skribilo-fragment-snippets-need-code-from-repo.gmi: Close
issue.

1 files changed, 6 insertions, 0 deletions

diff --git a/issues/skribilo-fragment-snippets-need-code-from-repo.gmi b/issues/skribilo-fragment-snippets-need-code-from-repo.gmi
index 0b0fdf6..74109ed 100644
--- a/issues/skribilo-fragment-snippets-need-code-from-repo.gmi
+++ b/issues/skribilo-fragment-snippets-need-code-from-repo.gmi
@@ -11,3 +11,9 @@ Also, evaluating an entire skribilo document on every search query may be costly
 Therefore, it might be worthwhile to inter snippet source texts into the xapian index itself—specifically in the document data field. This will of course increase the size of the xapian index considerably. But, storage is cheap, and there does not seem to be any more elegant way out.
 
 Until this issue is fixed, we have temporarily disabled snippets for skribilo fragments.
+
+## Resolution
+
+Search snippet source texts are now interred into the xapian index.
+
+* closed