view doc/log-signals.dox @ 26937:74c9f4f79825

Add 'jabber' to the signals output and NULL checking so it won't crash on Windows I'm baffled, but I currently get this signal output for the jabber-receiving-message signal: (22:27:44) jabber: Recv (ssl)(307): <message from='[e-mail]/desktop35DEABC4' to='[e-mail]/Testing' type='chat' id='purpleabb8c602'><active xmlns='http://jabber.org/protocol/chatstates'/><nos:x value='disabled' xmlns:nos='google:nosave'/><arc:record otr='false' xmlns:arc='http://jabber.org/protocol/archive'/></message> (22:27:44) signals test: received message (type=chat, id=purpleabb8c602, from=(null) to=chat) (nil) presence and IQ are fine...

/** @page log-signals Log Signals

 @signals
  @signal log-timestamp
 @endsignals

 @see log.h

 <hr>

 @signaldef log-timestamp
  @signalproto
char *(*log_timestamp)(PurpleLog *log, time_t when, gboolean show_date);
  @endsignalproto
  @signaldesc
   Emitted to allow plugins to customize the timestamp on a message
   being logged.
  @param log       The log the message belongs to.
  @param when      The time to be converted to a string.
  @param show_date Whether the date should be displayed.
  @return A textual representation of the time, or @c NULL to use a
          default format.
  @note Plugins must be careful of logs with a type of PURPLE_LOG_SYSTEM.
 @endsignaldef

*/
// vim: syntax=c.doxygen tw=75 et