History Log
CAUTION: THIS IS ALPHA QUALITY SOFTWARE. USE AT YOUR OWN RISK.
This is a plugin that logs to a text file all messages exchanged with contact or in a group chat. The text file is encoded in UTF-8.
The messages filename pattern accepts the following vars: (also, it support variables plugin)
%contact%
%contact_id%
%protocol%
%group%
%year%
%month%
%month_name%
%day%
The group chat filename pattern accepts the following vars: (also, it support variables plugin)
%session%
%protocol%
%year%
%month%
%month_name%
%day%
It also register itself with meSpeak and allows reading of messages (chat, url, fileand group chat events).
This plugin requires at least Miranda 0.7 and needs History Events to work.
To report bugs/make suggestions, go to the forum thread: http://forums.miranda-im.org/showthread.php?t=18488
To do
- ----
- In group chat, disconnects and renames are not logged
Changelog
. 0.0.0.5
* Fix for crash
* Fix for enable not working
+ Added highlighted messages as a separated meSpeak template
. 0.0.0.4
+ Added option to speak texts
* Per default disk log is disabled
. 0.0.0.3
+ Added BOM to files (editors should work better with this) - only for new files
+ Added group chat logging (dll needed to be renamed for this to work)
. 0.0.0.2
* Fix for multi-line messages (closes #41)
+ Added new variables to filename (closes #44)
+ Added option to ident multi-line messages (closes #43)
* Fix for invalid chars in msgs filename
. 0.0.0.1
+ Initial version
Reader Comments
1. In history events options (History->Events) you can select how long events will be kept in db. Just select ‘Only to view in message window’ there
2. I do not intend to do that
3. It is in my todo list, but very low priority. But I accept patches 
1. but it seems, that it don’t work or I don’t understand 
I enable option ‘Only to view in message window’, write some messages, exit miranda, then start miranda – and messages are still in history
oh…and I use dbx_3xSA as db driver.
It should work. That is a bug in History Events.Could you please open an issue at http://code.google.com/p/pescuma/issues/list and add to it your vi? Thanks
I’ve some good ideas, which may interests you
1. writing history to text files is great idea BUT – why isn’t possible to disable write it to *.dat file? Now it’s history logging twice…HistorySweeper is solution, but not ideal.
2. i miss an important feature – reading history (saved in text files) through some plugin like History++, or something like that.
3. but what I miss most is an option to export whole history to text files (whole history before instaling plugin)
But also great plugin, thanx for it