in7egral / mirotr

Automatically exported from code.google.com/p/mirotr
1 stars 0 forks source link

Option: Don't add OTR system message to history #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What shall be added?

Option called: "Don't add OTR system message to history"

Original issue reported on code.google.com by andrzej....@gmail.com on 17 Sep 2010 at 11:26

GoogleCodeExporter commented 9 years ago
Right, I forgot to do it.

Original comment by andreas....@student.kit.edu on 17 Sep 2010 at 2:58

GoogleCodeExporter commented 9 years ago
In r19, all messages except the following 2 can be automatically removed:

[OTR INFO] Requesting OTR encrypted session with 'prog test'
[OTR INFO] OTR encrypted session with 'prog test' has been terminated

Original comment by andreas....@student.kit.edu on 17 Sep 2010 at 3:06

GoogleCodeExporter commented 9 years ago
all messages except the following 2 can be automatically removed:

[OTR INFO] Requesting OTR encrypted session with 'prog test'
[OTR INFO] OTR encrypted session with 'prog test' has been terminated

Why this message can't be deleted?

Original comment by andrzej....@gmail.com on 17 Sep 2010 at 10:36

GoogleCodeExporter commented 9 years ago
These messages are sent before the session has started or after it has been 
finished.
To delete them, extra handling is required which needs some more work. 
The current state only required an additional option to be checked. Those two 
messages have to be filtered out via string comparison.
Just look at the changes in dbfilter.cpp in r19.

Original comment by andreas....@student.kit.edu on 18 Sep 2010 at 10:26