Bug 69970

Summary:	Actions are not shown correctly in history
Product:	[Unmaintained] kopete	Reporter:	Casey Allen Shobe <cshobe>
Component:	History Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	LO
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Casey Allen Shobe 2003-12-10 00:25:00 UTC

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.

Comment 1 Olivier Goffart 2003-12-10 14:23:09 UTC

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?]

Comment 2 Jason Keirstead 2003-12-10 14:37:59 UTC

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)

Comment 3 Casey Allen Shobe 2003-12-11 04:04:23 UTC

> [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.

Comment 4 jstuart 2004-02-12 20:41:26 UTC

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. :)

Comment 5 jstuart 2004-02-17 03:44:00 UTC

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)?

Comment 6 Justin Zobel 2021-03-09 22:41:14 UTC

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.

Comment 7 Christoph Cullmann 2024-09-18 18:28:12 UTC

Dear user, unfortunately Kopete is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.