branch: externals/xeft
commit 21465bba67c83a923b71808e1788ab1060745976
Author: Yuan Fu <caso...@gmail.com>
Commit: Yuan Fu <caso...@gmail.com>

    Update README and bump version
    
    * README.md: Update.
    * xeft.el: Bump version.
---
 README.md | 19 ++++++++++++++-----
 xeft.el   |  2 +-
 2 files changed, 15 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index cd123725c2..780bff6f3c 100644
--- a/README.md
+++ b/README.md
@@ -73,11 +73,20 @@ Functions you can customize to alter Xeft’s behavior:
   you ultimate control over which files to index.
 
 When Xeft reindexes a file, the changes are not immediately persisted
-to the DB file on disk. Instead Xeft periodically commit the changes
-to disk using an idle timer. The exact idle delay can be customized
-with `xeft-periodic-commit-timer-idle-delay`. But make sure to
-customize it before the first call of `xeft`, in which the idle timer
-is created.
+to the DB file on disk. Since version v3.4, Xeft periodically commit
+the changes to disk using an idle timer. The exact idle delay can be
+customized with `xeft-periodic-commit-timer-idle-delay`. But make sure
+to customize it before the first call of `xeft`, in which the idle
+timer is created.
+
+# Embedded images in text files
+
+Since version v3.5, Xeft can recognize embedded base64 encoding in the
+text, and skip them when indexing. If a stretch of text contains only
+characters used in base64 encoding, and is longer than 70 characters,
+it it considered base64 text and is skipped when indexing. This will
+cause Xeft to skip some longer urls since `/` is used in base64. The
+length threshold of 70 is hard-coded.
 
 # Building the dynamic module
 
diff --git a/xeft.el b/xeft.el
index c73528ff3c..738f4edcc6 100644
--- a/xeft.el
+++ b/xeft.el
@@ -5,7 +5,7 @@
 ;; Author: Yuan Fu <caso...@gmail.com>
 ;; Maintainer: Yuan Fu <caso...@gmail.com>
 ;; URL: https://sr.ht/~casouri/xeft
-;; Version: 3.4
+;; Version: 3.5
 ;; Keywords: Applications, Note, Searching
 ;; Package-Requires: ((emacs "26.0"))
 

Reply via email to