girzel
void-variable gnorb-org-trigger-actions
I have started trying to play with gnorb but I'm not getting very far. I have installed from elpa and added 3 lines to my init files (sent groups, tracking initialize and install defaults). When I try to gnorb-gnus-incoming-do-todo, I get:
Debugger entered--Lisp error: (void-variable gnorb-org-trigger-actions)
signal(void-variable (gnorb-org-trigger-actions))
gnorb-gnus-incoming-do-todo(nil)
funcall-interactively(gnorb-gnus-incoming-do-todo nil)
call-interactively(gnorb-gnus-incoming-do-todo nil nil)
command-execute(gnorb-gnus-incoming-do-todo)
yet if I look at the variable, it definitely is defined. What am I missing?
I have started trying to play with gnorb but I'm not getting very far. I have installed from elpa and added 3 lines to my init files (sent groups, tracking initialize and install defaults). When I try to gnorb-gnus-incoming-do-todo, I get:
Debugger entered--Lisp error: (void-variable gnorb-org-trigger-actions) signal(void-variable (gnorb-org-trigger-actions)) gnorb-gnus-incoming-do-todo(nil) funcall-interactively(gnorb-gnus-incoming-do-todo nil) call-interactively(gnorb-gnus-incoming-do-todo nil nil) command-execute(gnorb-gnus-incoming-do-todo)
yet if I look at the variable, it definitely is defined. What am I missing?
Well that's weird! I have tried to be very careful about letting users load some parts of Gnorb without using others, so I suppose that's what's happening here, but I'm very surprised that no one's run into this before.
Just to be clear, when you say the variable is "definitely defined", you just mean it exists in the file, right? If you examine it right after you get the above error, it must still be void/undefined, right?
I think I know where to put the right require, but in the meantime should just be able to explicitly (require 'gnorb-org) to work around this.
Thanks for looking at this.
When I say the variable is defined, I mean that C-h v gnorb-org-trigger-actions RET shows me the variable and it looks just fine. Very strange.
I should add that I am using emacs development version, aka 27.0.50...
I thought the error was due to me not requiring gnorb (I'm old skool and have only just recently started using the package system) but if I do so, I don't even get past my initialization. See attached screen capture of what happens when I start emacs with --debug-init.
With require 'gnorb-org, emacs starts up fine but I haven't had a chance to test further yet. I'll come back to this.
Okay, I've added (require 'gnorb-org) and things seem to work just fine now. Well, as I don't really know gnorb yet, I've only done some minimal testing but no errors so far!
Thank you.
I'm still totally perplexed by this. You say you get the above error (in the screen capture) when you do run (require 'gnorb) in your config? Is that before (package-initialize) or after? I just can't imagine why it would be calling ~gnorb-org-contact-link~, and not simply binding it. Is there any other background info you can give me?
On Wednesday, 9 May 2018 at 12:57, Eric Abrahamsen wrote:
I'm still totally perplexed by this. You say you get the above error (in the screen capture) when you do run (require 'gnorb) in your config? Is that before (package-initialize) or after? I just can't imagine why it would be calling ~gnorb-org-contact-link~, and not simply binding it. Is there any other background info you can give me?
It was after package-initialize. Not sure what other background information I can give. My .emacs is a 30+ year mess so I do have a setup that is likely to cause problems all the time... :-(
-- Professor Eric S Fraga, http://www.ucl.ac.uk/~ucecesf
I've fixed part of (possibly all of) the problem -- gnorb-install-defaults was missing a quote mark, that was why it was calling gnorb-org-contact-link. I'm not sure if it will solve the other problem too, but when 1.5.5 is available in the repos would you upgrade and give it a shot?