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, I found that one of my previous links saved was failing to open with the error "wrong-type-argument stringp nil" and the debugger gave the below result:
must somehow be missing the value of the string since the debug log shows the following block of code, making use of string-match, is passed a nil value. After some troubleshooting I found out that this was due to an unnecessary extra line between the heading and the properties drawer. I read through the readme again just to make sure I didn't miss something important about this, but didn't find something specific. It would probably be good to make the above piece of code slightly more robust for figuring out if there's a valid org-board save, and short of that then including a clear notice in the readme that the property drawer should directly follow the headline.
The text was updated successfully, but these errors were encountered:
Hi, I found that one of my previous links saved was failing to open with the error "wrong-type-argument stringp nil" and the debugger gave the below result:
I've been reading through the source code again and I'm guessing that the line of code:
must somehow be missing the value of the string since the debug log shows the following block of code, making use of string-match, is passed a nil value. After some troubleshooting I found out that this was due to an unnecessary extra line between the heading and the properties drawer. I read through the readme again just to make sure I didn't miss something important about this, but didn't find something specific. It would probably be good to make the above piece of code slightly more robust for figuring out if there's a valid org-board save, and short of that then including a clear notice in the readme that the property drawer should directly follow the headline.
The text was updated successfully, but these errors were encountered: