-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning (emacs): ... after-init-hook Should be defined as a symbol #81
Comments
Hello, Welcome back, I guess. :) Curious, have you tried Anyway, I think these warnings are coming from Helm, not from this package. |
Hi! Yes, I changed from org-rifle, to org-ql (org-ql-find-in-agenda). But lately it is hanging (it starts making a real-time search while I type, but suddenly it stops updating the results). After that, I have been using (my-multi-occur-in-matching-buffers). But I was missing our old rifle. I have been reading again the readme.org, and I think this kind of functions are not available in other search "engines": |
Yes, please do, otherwise the issue might go unresolved. Thierry is usually very responsive to reports.
That is probably this issue, which should get fixed eventually: alphapapa/org-ql#350 Please monitor that issue and try it again after it's fixed.
Most of those are or will be available in org-ql's commands as well. If there's a particular one you're missing, please open an issue on the org-ql tracker and we can talk about it. Since AFAICT the issue reported here is a Helm one, I'll close this issue now, but please let me know if you find otherwise. |
Hello @alphapapa here is the original issue and it seems you didn't fixed it ;-) |
Fixed on stable and master now. Thanks to all. |
Hi
After trying other searching options, I have come back to org-rifle. I like its real-time results, its options, and always works.
I am receiving a warning for each file of the agenda, when I eval helm-org-rifle-agenda-files:
⛔ Warning (emacs): Helm source ‘1-file.org’: after-init-hook Should be defined as a symbol
And it is giving me these warnings too:
The text was updated successfully, but these errors were encountered: