view doc/log-signals.dox @ 19654:6e9a16deb5b1

Fix the plugin loading issue Luke had noticed. This is a pretty weird bug that would've affected any new plugins being loaded. This bug remained hidden because we used to load the list of loaded plugins later. So this line, which I think was a typo to begin with, essentially didn't affect anything. Now that we load the preferences early, it was causing the list of loaded plugins to be rewritten at startup.

/** @page log-signals Log Signals

 @signals
  @signal log-timestamp
 @endsignals

 <hr>

 @signaldef log-timestamp
  @signalproto
char *(*log_timestamp)(PurpleLog *log, time_t when);
  @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.
  @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 tw=75 et