When the property's value is a org-link-bracket-re, it should not be
wrongly interpreted and processed as an emacs lisp expression
Current situation also prevents filtering items based on matching some
text in the link (it is ignored because is an emacs lisp expression)
---
lisp/org-collector.el | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lisp/org-collector.el b/lisp/org-collector.el
index 76ba7fb..fef438d 100644
--- a/lisp/org-collector.el
+++ b/lisp/org-collector.el
@@ -188,7 +188,8 @@ variables and values specified in props"
(mapcar (lambda (props)
(mapcar (lambda (pair)
(let ((inhibit-lisp-eval (or (string= (car pair) "ITEM")
- (string-match-p org-ts-regexp-inactive
(cdr pair)))))
+ (string-match-p org-ts-regexp-inactive
(cdr pair))
+ (string-match-p org-link-bracket-re (cdr
pair)))))
(cons (car pair) (org-babel-read (cdr pair)
inhibit-lisp-eval))))
props))
header-props)))
--
2.39.2
Pedro <pedro@cas.cat> writes:
> When the property's value is a org-link-bracket-re, it should not be
> wrongly interpreted and processed as an emacs lisp expression
>
> Current situation also prevents filtering items based on matching some
> text in the link (it is ignored because is an emacs lisp expression)
Applied, onto master.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>