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
When I run M-x ekg-notes-tag, I get the error message:
ewoc-locate: Wrong type argument: ewoc, nil
This is on GNU Emacs 28.2 (build 2, x86_64-w64-mingw32) of 2022-09-13, using the latest ekg downloaded today with the use-package statment in the ekg README.
The text was updated successfully, but these errors were encountered:
I downloaded emacs 28.2 and sqlite, but cannot reproduce this. Can you tell me more? Does this happen all the time? Can you call ekg-show-notes-with-tag with the same tag as the note you called ekg-notes-tag on, and does it work?
I don't see the error if I run ekg-show-notes-with-tag. I also don't see the error if I run ekg-notes-tag from within the notes window. Maybe that's the only place where it's intended to be used?
If so, maybe it would be best to only expose it to M-x completion when in a notes window.
Interesting, thank you, this makes sense. One thing to know is that you in emacs 29, you can have functions that show up only within the proper mode. That's already working correctly. But in emacs 28, you don't have that functionality, so indeed you can run ekg-notes-tag from any buffer, which isn't useful.
However, what should happen (and what does happen on my emacs 28.2), is that you should get an error message
This command can only be used in ‘ekg-notes-mode’
I'm not sure why you don't get that error message at the moment. Do you get prompted for a tag? You can try to debug ekg--current-note-or-error, which should be getting called in the interactive section of the command, and will throw the error if you aren't in the right mode.
When I run M-x ekg-notes-tag, I get the error message:
This is on GNU Emacs 28.2 (build 2, x86_64-w64-mingw32) of 2022-09-13, using the latest ekg downloaded today with the use-package statment in the ekg README.
The text was updated successfully, but these errors were encountered: