aboutsummaryrefslogtreecommitdiffstats
path: root/protocols/purple/purple.c
diff options
context:
space:
mode:
authordequis <dx@dxzone.com.ar>2015-03-03 20:18:43 -0300
committerdequis <dx@dxzone.com.ar>2015-03-03 20:18:43 -0300
commit56985aa93f09bef1400d41d6d79959dea4fa56d4 (patch)
tree925025b71c2343626d45f28175c01fbd42cf0238 /protocols/purple/purple.c
parentd93c8bebaf03ee9e7ed9eb94d9bb432a6517ce2b (diff)
Revert "purple: cleanup, remove one usage of static local_bee"
This reverts commit 5ff46180e5378acd6d103d9314175c78530bda7e. Turns out that libpurple really doesn't provide any context at all for some queries. Also, not going to say "Shouldn't affect anything" again. I'm getting good at writing code that looks good, but actually breaks stuff. That's not good. At all.
Diffstat (limited to 'protocols/purple/purple.c')
-rw-r--r--protocols/purple/purple.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/protocols/purple/purple.c b/protocols/purple/purple.c
index 0d830770..c3eb4a3b 100644
--- a/protocols/purple/purple.c
+++ b/protocols/purple/purple.c
@@ -1014,7 +1014,6 @@ static void *prplcb_request_action(const char *title, const char *primary, const
va_list actions)
{
struct prplcb_request_action_data *pqad;
- struct im_connection *ic = purple_ic_by_pa(account);
int i;
char *q;
@@ -1040,7 +1039,7 @@ static void *prplcb_request_action(const char *title, const char *primary, const
/* TODO: IRC stuff here :-( */
q = g_strdup_printf("Request: %s\n\n%s\n\n%s", title, primary, secondary);
- pqad->bee_data = query_add(ic->bee->ui_data, ic, q,
+ pqad->bee_data = query_add(local_bee->ui_data, purple_ic_by_pa(account), q,
prplcb_request_action_yes, prplcb_request_action_no, g_free, pqad);
g_free(q);