I encountered a problem where, if custom queries have words that have pages associated with them, then the automatic linker will link the query and wreck havoc.
For example, given the pages find, In Progress and NOW exist, if the following query is found in a page:
This Pull Request aims to address this issue and stop queries from being messed with. This is done by using regex to ignore content that is between the #+BEGIN_QUERY and #+END_QUERY prefix and suffix.
Documntation
In a real-world example, the query that I have used as an example (whcih is a query I use to see what I have in progress), actually gets transformed so the markers are showing the current date as stated in #70 and #27, for example:
I was unable to reproduce this issue for the automated tests. However, I was also unable to reproduce this issue while manually testing this fix, so hopefully this also fixes #70.
Fixes #27 and #70
Problem
I encountered a problem where, if custom queries have words that have pages associated with them, then the automatic linker will link the query and wreck havoc.
For example, given the pages
find
,In Progress
andNOW
exist, if the following query is found in a page:This currently gets transformed to:
Solution
This Pull Request aims to address this issue and stop queries from being messed with. This is done by using regex to ignore content that is between the
#+BEGIN_QUERY
and#+END_QUERY
prefix and suffix.Documntation
In a real-world example, the query that I have used as an example (whcih is a query I use to see what I have in progress), actually gets transformed so the markers are showing the current date as stated in #70 and #27, for example:
I was unable to reproduce this issue for the automated tests. However, I was also unable to reproduce this issue while manually testing this fix, so hopefully this also fixes #70.