view doc/Makefile.am @ 26879:7c58f6f50f16

Block/Unblock the signal handler when if it's unblocked/blocked. Trying to unblock the handler when it has not been blocked yet causes a 'handler not blocked' error message. When this message is added in the debug window, it goes into a mutex-lock from this line: gtk_list_store_append(debug_win->store, &iter); I have noticed this before on some occasions, where pidgin goes into a freeze when doing something from a signal-handler causes a debug message to be printed. Anyone knows why?

man_MANS =

if ENABLE_GTK
man_MANS += pidgin.1
endif

if ENABLE_GNT
man_MANS += finch.1
endif

EXTRA_DIST = \
	C-HOWTO.dox \
	PERL-HOWTO.dox \
	SIGNAL-HOWTO.dox \
	TCL-HOWTO.dox \
	TracFooter.html \
	TracHeader.html \
	account-signals.dox \
	blist-signals.dox \
	certificate-signals.dox \
	cipher-signals.dox \
	connection-signals.dox \
	conversation-signals.dox \
	core-signals.dox \
	dbus-server-signals.dox \
	funniest_home_convos.txt \
	finch.1.in \
	gtkaccount-signals.dox \
	gtkblist-signals.dox \
	gtkconv-signals.dox \
	gtklog-signals.dox \
	gtkimhtml-signals.dox \
	gtkrc-2.0 \
	imgstore-signals.dox \
	log-signals.dox \
	notify-signals.dox \
	pidgin.1.in \
	plugin-i18n.dox \
	plugin-ids.dox \
	plugin-signals.dox \
	savedstatus-signals.dox \
	sound-signals.dox \
	the_penguin.txt \
	xfer-signals.dox