From 6b3643c4d80507fa7e004fdb32b6768a45b4142c Mon Sep 17 00:00:00 2001
From: Arun Isaac
Date: Sun, 29 Jan 2023 01:03:44 +0000
Subject: skribilo: Temporarily disable search snippets.

* tissue/skribilo.scm (document-snippet-source-text): New method.
* issues/skribilo-fragment-snippets-need-code-from-repo.gmi: New
issue.
---
 issues/skribilo-fragment-snippets-need-code-from-repo.gmi | 13 +++++++++++++
 1 file changed, 13 insertions(+)
 create mode 100644 issues/skribilo-fragment-snippets-need-code-from-repo.gmi

(limited to 'issues')

diff --git a/issues/skribilo-fragment-snippets-need-code-from-repo.gmi b/issues/skribilo-fragment-snippets-need-code-from-repo.gmi
new file mode 100644
index 0000000..0b0fdf6
--- /dev/null
+++ b/issues/skribilo-fragment-snippets-need-code-from-repo.gmi
@@ -0,0 +1,13 @@
+# Search snippets for skribilo fragments need code from repo
+
+* tags: bug
+
+Skribilo documents are really programs. So, when generating search snippets for skribilo fragments, code from the repo may need to be executed. This is problematic since the web server process does not have the repository in its load path.
+
+The repository cannot simply be added to the load path since the web server process may be serving multiple repositories and we don't want them to interact.
+
+Also, evaluating an entire skribilo document on every search query may be costly. In fact, this expense of snippet generation applies equally well to other kinds of documents (issues, texinfo documents, etc.).
+
+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.
-- 
cgit v1.2.3