3 Jan 2005 00:35
Re: [jabber.el] External notifiers
Magnus Henoch <mange <at> freemail.hu>
2005-01-02 23:35:37 GMT
2005-01-02 23:35:37 GMT
Mario Domenech Goulart <mario <at> inf.ufrgs.br> writes: > I noticed that in jabber-alert.el there is some code to make "bridges" > between emacs-jabber and external programs like screen and ratpoison to > notify users about events. I made something similar for the Sawfish > window manager. > > Since it's possible that more external notifiers interfaces can be > implemented, what do you think about creating a directory called, say, > "external-notifiers" and move the code related to external programs from > jabber-alert.el to files under that directory? I think that's a really good idea. The ability to have external notifiers was one of the things that made me start using jabber.el. They should be preserved, encouraged and evolved. While looking at your patch, I noticed that writing alert hooks currently is far too repetitive. It requires writing four (used to be three) separate functions with different argument lists (and you are consistently only interested in the last argument), all containing exactly the same (possibly quite complicated, and possibly needing to be changed) code, and it requires adding each function to the options of the corresponding hook variable, so people can find it in Customize. It shouldn't be like that; after all, this is Lisp, not C++. So I wrote a macro `define-jabber-alert', which is used like this: (define-jabber-alert sawfish "Display a message through the Sawfish window manager"(Continue reading)
Since as I see the logs are saved as Lisp data, it would be quite
straightforward to read them by ee. However, I suspect that there
are no initial `[' or `(' and final `]' or `)' to read all vectors
as one Lisp object. In any case, this is not a problem.
I will install emacs-jabber in the next few days and see
what I can do with it.
RSS Feed