Mercurial > pidgin
view README.dbus @ 11217:f854402837ba
[gaim-migrate @ 13349]
The history plugin really should require logging be on. Otherwise, you can end up seeing a really old conversation instead of the "last" conversation. I've made this change.
Now, the history plugin can't be silently failing to do its job if logging is disabled. I've coded it to display a warning dialog under the following conditions:
1) The user enables the history plugin and neither IM nor chat logging is enabled.
2) The user starts Gaim with the history plugin and no logging enabled.
3) The user disables logging while the history plugin is enabled.
I thought about automatically disabling the history plugin after displaying the dialog, but I imagine (hope?) people will enable the history plugin, see the dialog, and enable logging. If this is what happens, they would be confused if the history plugin automatically disabled itself when it displayed the dialog.
This should address RFE 1241878, "History plugin should have a more helpful description".
committer: Tailor Script <tailor@pidgin.im>
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Tue, 09 Aug 2005 05:20:07 +0000 |
parents | 2eca9ed49469 |
children |
line wrap: on
line source
This file describes how to compile and run gaim with dbus support. Hopefully, most of the steps from point 3 will soon be automated. 1. Make sure you have the latest version (0.34) of the dbus library installed, including glib bindings. http://www.freedesktop.org/Software/dbus 2. Compile gaim ./configure --enable-dbus make make install 3. Configure your dbus instalation for gaim A. Find your dbus session configuration file, usually /etc/dbus-1/session.conf B. In that file, find the <servicedir> section. This section contains the directory that stores files describing services, usually /usr/share/dbus-1/services C. Copy src/dbus-gaim.service to that directory D. Edit the dbus-gaim.service file you've just copied, and replace the path in the "Exec=" line with the path to your gaim executable. 4. Start Session DBUS if you haven't done it already eval `dbus-launch --session` export DBUS_SESSION_BUS_ADDRESS DBUS_SESSION_BUS_PID These commands will set the two above shell variables. These variables must be set before running any dbus-aware programs. Start gaim as usual. To communicate with it, use "gaim-send". When you execute gaim-send, the dbus system will automatically start a gaim process if one is not running already.