You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. First, thank you so much for this. I have it installed and also have the express note templater from the demo vault working in my translation (although it took me 2 hours to realize my translation had a space at the end of each H6 line which was causing the verses not to pop up in the picker!)
I use a single note for each Bible chapter to put my notes on as well as putting references during sermon notes back to the bible ... and leave the Bible files themselves unadulterated (I don't mark up the origin, I mean). While I am reading the Bible, any references for things I myself have written will show up using the Strange New Worlds plugin... basically showing me "this verse has some notes somewhere, go see!"
If I do a single verse reference in my personal note, like [[Ezek 21#10]] I see the outgoing link fine and the incoming link fine in the Bible. Looks like:
and in the Bible it shows like:
However, if I do the range reference in my note, I see this fine:
but in the Bible, I don't see the SNW reference:
There is a backlink to my note:
And it even appears to show fine in the SNW sidebar:
To be clear, my goal is to have a SNW reference from the Bible back to my notes, whether the reference is a single verse or a range of verses. I realize I might not be able to get a SNW reference to each of the verses in the range (like in the example, have SNW show a number on verse 9, verse 10, verse 11, AND verse 12) but I would at least like to have a reference to verse 9 so that I know I have personal notes for that particular verse.
I know this seems like a bug maybe in SNW, but I was wondering if anyone had run into this and/ or sees the same thing? Since this format of range seems specific to this link-heading-range plugin, I thought I would ask here. It isn't a matter of a refresh in order to show these SNW numbers- I have reloaded the app and no difference.
Thanks!
Aaron
The text was updated successfully, but these errors were encountered:
Hi. First, thank you so much for this. I have it installed and also have the express note templater from the demo vault working in my translation (although it took me 2 hours to realize my translation had a space at the end of each H6 line which was causing the verses not to pop up in the picker!)
I use a single note for each Bible chapter to put my notes on as well as putting references during sermon notes back to the bible ... and leave the Bible files themselves unadulterated (I don't mark up the origin, I mean). While I am reading the Bible, any references for things I myself have written will show up using the Strange New Worlds plugin... basically showing me "this verse has some notes somewhere, go see!"
If I do a single verse reference in my personal note, like
[[Ezek 21#10]]
I see the outgoing link fine and the incoming link fine in the Bible. Looks like:and in the Bible it shows like:
However, if I do the range reference in my note, I see this fine:
but in the Bible, I don't see the SNW reference:
There is a backlink to my note:
And it even appears to show fine in the SNW sidebar:
To be clear, my goal is to have a SNW reference from the Bible back to my notes, whether the reference is a single verse or a range of verses. I realize I might not be able to get a SNW reference to each of the verses in the range (like in the example, have SNW show a number on verse 9, verse 10, verse 11, AND verse 12) but I would at least like to have a reference to verse 9 so that I know I have personal notes for that particular verse.
I know this seems like a bug maybe in SNW, but I was wondering if anyone had run into this and/ or sees the same thing? Since this format of range seems specific to this link-heading-range plugin, I thought I would ask here. It isn't a matter of a refresh in order to show these SNW numbers- I have reloaded the app and no difference.
Thanks!
Aaron
The text was updated successfully, but these errors were encountered: