Summary: | Private messages sent from channel contexts should be logged in the appropriate query log instead of the channel's log | ||
---|---|---|---|
Product: | [Applications] konversation | Reporter: | JPD <tightcode> |
Component: | logging | Assignee: | Konversation Developers <konversation-devel> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | hein, nalvarez, ompaul |
Priority: | LO | ||
Version: | 1.5-rc1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Bug Depends on: | |||
Bug Blocks: | 192524 |
Description
JPD
2005-02-27 14:04:25 UTC
You can use /query person to have it logged. Actually the fact that /msg is still logged in the channel you do it in is actually quite bad. Maybe what we should do is simply have a list of nicks that aren't logged at all, then ship with the defaults of nickserv and whatever other popular password nicks are. If we do this then we could log /msg as well. I was thinking that perhaps you could log the /msgs to the same logfile a query window would use. *** Bug 265950 has been marked as a duplicate of this bug. *** *** Bug 245752 has been marked as a duplicate of this bug. *** Git commit 00c0709eaac0fbe9798bd7141e6a94ac68a54156 by Nicolás Alvarez. Committed on 09/04/2012 at 04:11. Pushed by nalvarez into branch 'master'. Fix misleading log formatting when /msg'ing from a channel window. When doing "/msg foo bar" in a channel, we used to log "<foo> bar" in the channel log. This is very misleading, since it looks as if 'foo' said it rather than sending it *to* foo. This commit changes it to "<-> foo> bar", which looks a bit odd to me but it's consistent with what gets shown in the ircview. This partially fixes the complaints in bug 100369. The other part of that bug is logging the message in the recipient's log instead of the channel's, but that's apparently quite hard. M +5 -1 src/viewer/ircview.cpp http://commits.kde.org/konversation/00c0709eaac0fbe9798bd7141e6a94ac68a54156 Nicolas, any news on this for the upcoming 1.5 version? This is still an issue. |