Version: (using KDE Devel) Installed from: Compiled sources Message from #kopete (#kopete) @ 10:40:28 is away: I'm busy Aside from the problem that this is shown as from #kopete (I think already reported), it is shown as a message instead of an action.
gloups, action messages are actualy not supported by the history plugin. a simple hack which is certenly the simplest way to fix the problem is to add /me to messages before writing them in the history file. (but isn't verry portable) [P.S: I was about to confirm the bug, but the bug is already set as NEW, i think the reporter of the bug shouldn't set it to new dirrectly. don't you think?]
Subject: Re: [Kopete-devel] Actions are not shown correctly in history On December 10, 2003 9:23 am, Olivier Goffart wrote: > a simple hack which is certenly the simplest way to fix the problem is to > add /me to messages before writing them in the history file. (but isn't > verry portable) Wouldn't it be simpler to just save the message type along with the message when you write it to disk?? It's just an Enum (int)
> [P.S: I was about to confirm the bug, but the bug is already set as NEW, i > think the reporter of the bug shouldn't set it to new dirrectly. don't you > think?] Umm...#1, it IS most certainly an accurate reporting of the problem, otherwise I would have said so or set it back to unconfirmed myself, so I really don't see any problem with this. #2, when you have anything but the most basic account on bugzilla, new bug reports automatically become NEW instead of UNCONFIRMED. I have no control over it. Generally such accounts are granted to people who are fairly competent about reporting bugs, and don't report invalid bugs very often (much less often than you would otherwise have to set unconfirmed --> new for that user's bugs.
I don't think this is that severe of a problem so I'm bumping severity down one. If wrong, please slap me and then bump it up. :)
Ok, for all these bugs marked as new in the history plugin. :) Can I bump all of these to assigned? IE is someone working (or going to work on em)?
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.