Bug 148783 - Mode prefixed channel messages treated as queries
Summary: Mode prefixed channel messages treated as queries
Status: ASSIGNED
Alias: None
Product: konversation
Classification: Applications
Component: protocol (show other bugs)
Version: 1.5-rc1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: argonel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-12 23:52 UTC by argonel
Modified: 2021-01-14 05:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description argonel 2007-08-12 23:52:42 UTC 
Version:           1.0.1+ #3212 (using KDE 3.5.5, Debian Package 4:3.5.5a.dfsg.1-1 (testing/unstable))

probably affects notices as well.

<argnl> /msg @#konversation test

[17:45] >> :argnl!i=ident@konversation/developer/argonel PRIVMSG @#konversation :test 

result: a new query window created for argnl. looks like the modes are stripped on receipt. 

sending appears to work ok, albeit with difficulty as there is no shortcut. autoreplace, maybe?

sent ones look funny too: [18:09] <-> @#> test
Comment 1 Justin Zobel 2020-11-30 03:11:04 UTC 
Eli is this still an issue on current konversation versions?

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 2 Bug Janitor Service 2020-12-15 04:33:55 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 argonel 2020-12-15 06:21:53 UTC 
I don't think anyone's worked on this.
Comment 4 Justin Zobel 2020-12-15 06:22:54 UTC 
(In reply to Eli MacKenzie from comment #3)
> I don't think anyone's worked on this.

Thanks for the update but can you please check if this is still an issue?
Comment 5 Bug Janitor Service 2020-12-30 04:34:15 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2021-01-14 04:33:45 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 7 argonel 2021-01-14 05:36:48 UTC 
Whoops, forgot about this one.