laynor / enotify

A network notification system for emacs
12 stars 1 forks source link

Problems with startup #1

Open svs opened 11 years ago

svs commented 11 years ago

Hello, first of all, thanks for the effort with enotify. This is exactly what I need to put a cherry on top of my dev environment! However, I have been having some issues that I was hoping you could help me with.

First of all, emacs complains thusly when loading

Warning (initialization): An error occurred while loading `/Users/svs/.emacs':

Symbol's function definition is void: enotify/plugin:register

To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file.  Start Emacs with
the `--debug-init' option to view a complete error backtrace.

Also, spectator-emacs compains thusly

spectator-emacs                                                                                                         rvm:ruby-2.0.0-p195@mainapp
{"--config"=>".spectator-emacs", "--help"=>false, "--version"=>false}
======= OPTIONS =======
enotify_port => 5000
enotify_host => localhost
notification_messages => {:failure=>"F", :success=>"S", :pending=>"P", :error=>"E"}
notification_face => {:failure=>:":failure", :success=>:":success", :pending=>:":warning", :error=>:error}
=== Connecting to emacs... Success!
--- Waiting for changes...
[Listen warning]:
The blocking parameter of Listen::Listener#start is deprecated.
Please use Listen::Adapter#start for a non-blocking listener and Listen::Listener#start! for a blocking one.

Also, I see this message in emacs

error in process filter: condition-case: Enotify: Bad message from <127.0.0.1:50132>:: (:register "project foobar" :handler-fn "tdd") -> (error "Enotify: invalid slot message handler for slot-id \"project foobar\"")
error in process filter: Enotify: Bad message from <127.0.0.1:50132>:: (:register "project foobar" :handler-fn "tdd") -> (error "Enotify: invalid slot message handler for slot-id \"project foobar\"")

Any ideas what I should do next?

laynor commented 11 years ago

Hi, sorry for the late reply, I did not notice this issue! Did you require enotify-tdd in your emacs config? This is my initialization:

(add-to-list 'load-path (concat user-emacs-directory "site-lisp/enotify/"))
(setq enotify-use-next-available-port t)
(require 'enotify)
(require 'enotify-tdd)
(enotify-minor-mode t)

You can try it and see if you have problems