Bug 265950 - Privmsgs sent via commands are stored wrong in logs
Summary: Privmsgs sent via commands are stored wrong in logs
Status: RESOLVED DUPLICATE of bug 100369
Alias: None
Product: konversation
Classification: Applications
Component: logging (show other bugs)
Version: Git
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-10 01:40 UTC by Nicolás Alvarez
Modified: 2011-02-10 08:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolás Alvarez 2011-02-10 01:40:29 UTC
If I'm in #konversation and I type "/msg joe hello world", it sends "hello world" as a private message to 'joe', but the message is logged in #konversation.log instead of joe.log.

That by itself isn't so bad, but the way it's stored is highly misleading: "<joe> hello world". It looks as if 'joe' was the *sender* of the message instead of the *recipient*, and enforces the wrong impression that the message went to #konversation rather than being private.

It wouldn't be so bad if it showed "private message to joe: hello world" (or something like that) in #konversation.log, but ideally it should store "<myownnick> helloworld" in joe.log instead; just as if the message was sent from a query window instead of using /msg.

/query has the same problem as /msg (unsurprisingly).
Comment 1 Peter Simonsson 2011-02-10 08:06:49 UTC

*** This bug has been marked as a duplicate of bug 100369 ***